# Adjusting Cache Behavior Settings
# Options for Customizing Cache Behavior and Access Control
- Respect HTTP Header
- Ignore 'Cookies'
- Ignore 'Vary'
- Origin use HTTP
- Force HTTPS
- Enable HSTS
- Enable GZIP at CDN
- Default TTL
# Respect HTTP Header
Enable this option if you want the CDN to handle content caching based on standard HTTP headers.
If your origin server doesn't specify cache-related HTTP headers, disable this option. The CDN will then cache content based on file types.
# Ignore 'Cookies'
Forces the CDN to cache content even when requests contain cookies (By default, CDN doesn't cache content with cookies since it may contain user-specific data)
WARNING
Enabling this option may cause CDN to cache content that shouldn't be cached (e.g., private data from authenticated users). Carefully evaluate whether this option is necessary for your use case.
For technical consultation, contact support@byteark.com
# Ignore 'Vary'
Forces the CDN to cache content regardless of Vary header specifications.
WARNING
Enabling this option may cause incorrect caching of CORS-related HTTP headers. Carefully evaluate whether this option is necessary for your architecture.
For technical consultation, contact support@byteark.com
# Origin use HTTP
Enable this if your origin server doesn't support HTTPS protocol. This forces the CDN to request content from the origin server using HTTP protocol only.
# Force HTTPS
Forces all client requests to use HTTPS protocol. Any HTTP requests will be redirected to the same domain and path using HTTPS protocol.
# Enable HSTS
Enables HTTP Strict Transport Security (HSTS) related HTTP headers, informing clients that this domain must be accessed via HTTPS only.
TIP
For more technical details about HTTP Strict Transport Security (HSTS) (opens new window)
# Enable GZIP at CDN
Enables GZIP compression so that the CDN can deliver content to users in a compressed format if the client supports it.
# Default TTL
Specify default Time-To-Live (TTL) of cache objects. The default is 60 minutes.