In these settings you can manage how your pull zones work.
- Change server of origin – here you can change the source of incoming files / data
The purpose of the origin server is to process and respond to incoming internet requests from internet clients. An origin server is a computer that runs one or more programs designed to listen to and process incoming Internet requests. The origin server can take full responsibility for content hosting for a web-owned property such as a website. As long as the traffic does not exceed what the server can process, latency is not the primary concern.
- Time to live – time to live for files in the cache memory
The time to live (TTL) is the amount of time an object is kept in the cache system before it is deleted or refreshed. In the context of a CDN, TTL usually refers to the content cache, which is storing copies of a site’s resources (e.g., Images, Prices, Text) on CDN proxies to increase page load speed and reduce the bandwidth utilization of the origin server. In this context, TTL regulates these copies’ refresh rate, ideally ensuring that “outdated” versions of your content are not shared with your site visitors.
- Use origin shield – Reduce load on origin server by allowing CDN nodes to reqest fields via a shield node that maintains it’s own cache.
Origin Shield can help improve the cache hit distribution ratio as it provides an extra layer of buffering before origin. When you use Origin Shield, all requests from all cache layers to your source go through Origin Shield, which increases the likelihood of a cache hit. Origin Shield Reduced Source Loading – May further reduce the number of simultaneous requests sent to the same object’s origin. When you turn on Origin Shield in a region with the lowest latency to your source, you can get better network performance.
- Min. Requests to cache – the minimum number of requests that users should make to run the cache
- Truncate URL param – thanks to this option your url’s will be more user-friendly
URL shortening is important as it is easier for recipients to trust and click on the shorter link (provided it is shared from a credible source) compared to the longer one. The shortened link is better seen by search engine spiders and affects the SEO of your site.
- Ignore Cache Control – Ignore cache check headers set on the source server.
Every time the same request comes to the service, the response is retrieved from the cache and passed to the user. If the cache state is “off,” the request is sent directly to the server for a response.
- CORS header – Ability to share resources between different origin
CORS relies on how browsers send a “preflight” request to the server serving a resource cross-origin to verify that it will allow the actual right. In this preflight, the browser sends headers that indicate the HTTP method and headings used in the actual request.
- Cache gzipped content separately – enable if origin can gzip-archive the content, it will be cached separately.
- HTTPS – HTTPS protocol support
An encrypted version of the HTTP protocol. Contrary to the communication of unencrypted text over HTTP client-server, HTTPS encrypted data using the SSL protocol, while the TLS protocol is currently used for this purpose. This prevents interception and alteration of transmitted data.
- HTTPS / 2 – support for HTTPS / 2 protocol
HTTP / 2 is a specification of how the server should communicate with the browser so that data is transferred as quickly as possible.
- Shared SSL – using the zone in HTTPS mode with our certificate, i.e. for the system domain
An SSL certificate installed on the web server makes it easy to share the hosting environment. The shared SSL certificate is installed on multiple sites that share the same IP address. Therefore, each site does not receive its certificate. As a result, your URL will not be in the certificate details; it will only include your hosting provider’s URL. These SSL certificates are signed, installed, and managed by hosting providers or CDN (Content Delivery Network).
- Redirect to HTTPS – automatic redirection of HTTP requests to HTTPS
Without SSL, your website will be insecure for your visitors. Therefore, it is imperative to use an SSL encrypted connection for security, availability, or PCI compliance reasons. Redirection from HTTP to HTTPS becomes very important.