---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Cache-Control HTTP Header Value \[Updated in Security Center 1.3 and removed in 1.5\]

# Cache-Control HTTP Header Value \[Updated in Security Center 1.3 and removed in
1.5\] {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Use the glide.http.cache_control property to set the default
cache-control value in the HTTP response headers that the ServiceNow AI Platform sends when
requesting static content data for a page. Examples of static content include images, CSS, and
JavaScript rendered from within, for a page.
The glide.http.cache_control property sets the default Cache-Control value in HTTP response headers to private or public. The default is private.{#sc-cache-control-http-header-value__table_exb_mjr_slb__entry__2}

| Value | Description |
|-|-|
| private | Static content can be cached at the browser (client) level, but not at the proxy server level. |
| public | Static content can be cached at the browser (client) level, and also at the proxy server level. |
[ ]

{#sc-cache-control-http-header-value__table_exb_mjr_slb}

The Expires value in the HTTP response headers control when the static content expires, and
has a default value of 369 days. To manually override the default value, use the
glide.http.expire.days property.

Hinweis:  
You can use the glide.http.cache property designate whether to enable or disable setting of the Cache-Control and Expires values in HTTP response headers. Its default is true, which allows you to set the:

* Cache-Control value default using the glide.http.cache_control property.
* Expires value default using the glide.http.expire.days property.
{#sc-cache-control-http-header-value__ul_bd1_whr_slb}

## More information {#sc-cache-control-http-header-value__section_more_information}

{#sc-cache-control-http-header-value__table_ajc_b43_3kb__entry__2}

| Attribute | Description |
|-|-|
| Property name | glide.http.cache_control |
| Configuration type | System Properties (/sys_properties_list.do) |
| Category | [Configuration](https://servicenow-prod.fluidtopics.net/s9Iz8esR6282THUNXoEpzg "The Configuration category ensures applications have a secure build environment and hardened third party library components. Specifically, ensuring a build and deploy pipeline is repeatable and includes automated testing and prevents known security issues from being deployed. This includes keeping dependencies up to date and free from known vulnerabilities.") |
| Purpose | To configure the Cache-Control HTTP response header value for static content. |
| Recommended value | private |
| Default value | private |
| Security risk rating | 4.3 |
| Functional impact | Sets the default Cache-Control value in an HTTP response header. |
| Security risk | (High) If you set this property to public, instances with CDN/proxies may cache static content and render without authentication. * private is a more appropriate setting for instances with CDN/proxy setup. * If an the instance does not have a CDN/proxy setup, either value should be fine. {#sc-cache-control-http-header-value__ul_gwc_byx_slb} |
[ ]

{#sc-cache-control-http-header-value__table_ajc_b43_3kb}

To learn more about adding or creating a system
property, see [Add a system property](https://www.servicenow.com/docs/access?context=t_AddAPropertyUsingSysPropsList&version=australia&pubname=australia-platform-administration&ft:locale=en-US).