URL Query Literal

Applies To:

HTTP LargeThis platform has been optimized to cache and deliver static content (e.g., HTML, CSS, JavaScript, ISO, multimedia, and software downloads, etc.) over HTTP or HTTPS.

HTTP SmallLegacy. If you are currently serving traffic over this platform, then you may continue to do so. However, we recommend that you serve your traffic over our more robust HTTP Large platform.

ADNThe Application Delivery Network platform has been optimized to deliver dynamic content (e.g., login credentials, account information, etc.) over HTTP or HTTPS. Typically, user-specific and database-driven content are served over this platform.

Rules EngineAllows the customization of how requests are handled by our CDN service. It may be used to override the default response provided by an origin server, CDN settings, and the default edge server behavior. - Basic

Category: URL

Purpose: Identifies requests by whether the query string of the requested URL matches a literalThis type of value does not assign a special meaning to characters. The only exception is % which is used for URL encoding. value.

Key information:

The value associated with this match condition will be compared against the entire request's query string.
For the purposes of this option, a query string starts with the first character after the question mark (?) delimiter for the query string. Therefore, the text specified in the Value option should not include a leading question mark (?).
The value associated with this match condition may be defined using any combination of numbers, letters, and/or symbols. All characters, with the exception of the % symbol, will be treated as a fixed value and cannot take on a special meaning.
The case-sensitivity of query string comparisons is determined by the Ignore Case option.

Certain characters require URL encoding. Use the percentage symbol to URL encode the following characters:

Character	URL Encoding
Space	%20
&	%26
%	%25

Matching against URLs that contain non-US-ASCII characters requires that you specify encoded Unicode characters (e.g., %E3%81%93).
- Encode all Unicode characters before setting the Value option. This match condition only accepts encoded Unicode characters.
  
  Example:
  
  You should include the following characters instead of こんにちは when defining this match condition's value:
  
  %E3%81%93%E3%82%93%E3%81%AB%E3%81%A1%E3%81%AF
- The majority of user agents (e.g., web browsers) encode non-US-ASCII characters in the request's query string before submitting the request to our CDN. By default, our CDN service does not decode those characters.
  
  Curl does not encode non-US-ASCII characters. If you would like to test this match condition using curl, then you will need to create a mutually exclusive match section (i.e., IF / ELSE IF). Each conditional expression within that statement should contain this match condition with the Encoded option set to different values.
- Use the Encoded option to determine whether your match value, as defined in the Value option, will be decoded prior to comparison with the request's query string. You must set this option to Yes when either of the following conditions are true:
  - A URL normalization customization has been applied to your traffic.
  - The request's query string contains encoded Unicode characters (e.g., %E3%81%93).
  Enabling this option ensures that your match value remains encoded.
  
  If both of the above conditions are not applicable, then you should use the default configuration (i.e., No) which allows our service to decode your match value.
Due to the manner in which cache settings are tracked, this match condition is incompatible with the following features:
- Complete Cache Fill (End-of-Life)
- Default Internal Max-Age
- Force Internal Max-Age
- Ignore Origin No-Cache
- Internal Max-Stale
- URL Rewrite