> For the complete documentation index, see [llms.txt](https://docs.link11.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.link11.com/product-guides/secure-cdn/interface/instances/cdn-location-general-settings.md). # CDN Location General Settings
When adding or editing a CDN location, the dialog above appears. This page provides general CDN configuration options for specific sections of a site. Other configuration options are available in the [Caching Settings](/product-guides/secure-cdn/interface/instances/cdn-location-caching-settings.md). ## **Location** Specifies the path within the origin. Each location must specify a Location Type, which defines how the path is matched (see below). The type for the root or `/` location is always recursive (this cannot be changed) and will apply to all paths not explicitly defined within the CDN service. ## **Type** The following types are supported: * **Exact Location**. Applies only to requests that exactly match the specified path. Examples: `/index.html`, `/media/logo.png` * **Regex Location**. Applies to paths matching a regular expression pattern: * Supports Perl-compatible regular expressions (PCRE) * Not case-sensitive * Can be reordered to control priority * Use this option to handle: * Dynamic patterns (/blog/\[0-9]{4}/.\*) * File types (.jpg, .png, etc.) * **Recursive Location**. Applies to all requests that begin with the specified path, including subdirectories. Example: `/assets/` applies to /assets/img/, /assets/css/, etc. {% hint style="info" %} Note that File Extension Locations, used in a previous version, have been deprecated. These use cases should now be handled with *Regex Locations*; see discussion below. {% endhint %} ### Location matching priority Locations are matched and applied in the following priority order: 1. Exact Locations 2. Regex Locations 3. Recursive Locations 4. Root Location (always applied last) **Important Behavior:** * Exact and Recursive Locations are sorted automatically by specificity. * Regex Locations can be manually reordered via the “Change Priority” option in the Actions menu. * The Root Location (`/`) is the default fallback and cannot be deleted. ### Using Regex to match file types To apply settings to specific file types (e.g., .jpg, .png), use the *Regex Location* Type. Template: `^\/`${LOCATION\_PREFIX}`\/.+\.(`${EXT\_1}|${EXT\_2}`)\/?$` * Replace ${LOCATION\_PREFIX} with the desired folder path * Replace ${EXT\_1}|${EXT\_2} with the desired file extensions Example: `^\/my\/subfolder\/.+\.(jpg|png)\/?$` matches: * /my/subfolder/image1.jpg * /my/subfolder/photo.png ## **Host Header** Customers can configure the “Host” header to match something other than the $host directive typically forwarded to the origin. ## **Proxy Min Uses** Select the minimum number of requests after which an origin response will be saved to the CDN cache. In other words, this is the number of requests that will be served without causing the response to be cached. ## **CORS** (Cross Origin Request Sharing) Enabling this setting will include the following headers in the response from the Link11 proxy servers and the client: * **access-control-allow-credentials**: true * **access-control-expose-headers**: link, set-cookie * **access-control-allow-origin**: $access-control-allow-origin When enabled the following option will become available: ### **Access Control Allow Origin** If [CORS](#cors) is On, but the Access Control Allow Origin field is blank, the $access-control-allow-origin will be set to “\*”. If the customer is missing this header, there might be an issue with the Access Control Allow Origin variable. {% hint style="info" %} This field contains the origins that should be allowed by CORS. This option supports regex, and the value entered can be very complex. Currently, this option is only editable by Link11. To add a value, please contact your Link11 representative. {% endhint %} ## **Error Pages Interception** When [custom error pages](/product-guides/web-ddos/interface/instances/http-settings.md#error-pages) have been defined in Web DDoS, and this setting is enabled, those error pages will be used in Secure CDN as well. ## **IP ACL Limits** Use an IP Access Control List (ACL) to limit public access for specific IP ranges. ## **Browser Cache Expiration** Set the time when the cached items expire in the client browser. Note that an expired header set by the customer overrides this setting, unless otherwise configured in the [Caching Settings](/product-guides/secure-cdn/interface/instances/cdn-location-caching-settings.md). ## **Advanced Query String** Specifies the http GET parameters that should be stripped from request URLs. {% hint style="info" %} This setting is provided here for legacy purposes only. It has been replaced by the [Cache Key](/product-guides/secure-cdn/interface/instances/cdn-location-cache-key.md) features. {% endhint %} ## **Compression** Allows admins to enable file compression on content stored on the CDN. Admins can choose between Gzip and Brotli compression algorithms. If a compression method (i.e., something other than *None*) is selected, a field for additional MIME types will appear. ### Add MIME types for Compression
This allows admins to specify additional file types for compression. Some types will be compressed by default already (those listed in the caption of the *Compression* field:`text/plain`, `text/css`, `text/xml`, and so on). If any types are desired beyond these, they should be entered here. Acceptable file types are in accordance with [RFC 6838](https://datatracker.ietf.org/doc/html/rfc6838#section-4.2) (but see warning below): `application`, `audio`, `image`, `message`, `model`, `multipart`, `text`, and `video` . {% hint style="warning" %} Although MIME types for binary formats (such as image, video, etc.) are accepted, their use is discouraged. Most binary file types (jpg, PDF, mp4, etc.) are already compressed, and subjecting them to additional compression by the CDN can create undesirable results. {% endhint %} {% hint style="info" %} The syntax is \[*type*]/\[*subtype*], without parameters. For example, `text/html` will be accepted, but \ `text/html; charset=UTF-8` will be rejected. {% endhint %} Multiple types can be entered, separated by spaces (e.g., `application/x-freearc text/csv`). If duplicate entries occur, or a default type is entered, the system will accept the entries without producing an error. ## **Max File Upload Size** Specifies the maximum size of files that can be uploaded through the CDN. Be aware that if you are using Web DDoS on the same domain, there is a separate setting for Max POST size ([Instance → HTTP Settings](/product-guides/web-ddos/interface/instances/http-settings.md#max-post-size)) that needs to be equally adjusted for the file upload to work. ## **Origin Load Balancing** For activating Load Balancing between multiple origin servers. ## **HTTP Origin Address and Port** Defines the origin address, port and protocol for requests that are received via HTTP. You can choose between the HTTP and HTTPS protocol. If any [Load Balancers](/product-guides/secure-cdn/interface/load-balancing.md) were configured and enabled, they will be available for selection here as the destination for traffic. ## **HTTPS Origin Address and Port** Defines the origin address, port and protocol for requests that are received via HTTPS. You can choose between the HTTP and HTTPS protocol. If any [Load Balancers](/product-guides/secure-cdn/interface/load-balancing.md) were configured and enabled, they will be available for selection here as the destination for traffic. ## **Origin Timeouts** Defines the source read and connection timeouts for the origin.