Tab – Advanced

These are settings that are not included in the basic configuration.

Section - Advanced Virtual Host Settings

Session cookie path and domain

Specifies the cookie path and domain field for Airlock Gateway's session cookie if the cookie is created inside this virtual host.

Keep-Alive timeout (seconds)

Specifies the HTTP keep-alive timeout in seconds for this virtual host. A value of 0 (zero) disables the HTTP keep-alive function.

Download PDFs as attachments

If this option is enabled, PDF documents (detected by their content-type application/pdf) are always downloaded as attachments (not as "inline" document within the browser).

Allow encoded slashes (%2F)

Specifies whether encoded slashes (%2F) are allowed in URL path. Attention: combinations of client certificates per mapping and enabled encoded slashes in the same virtual host might result in configurations where client certificate evaluation might be evaded. Please contact Airlock support.

Section - Server Alias Names

Specifies additional server aliases for this virtual host.

Section - Path Redirects

Airlock Gateway provides dynamic URL redirects for each virtual host. If a matching redirect path is detected, the client will be redirected to the redirect destination. These redirects can be used to map special external URLs to real application URLs. URLs of this form are often used in marketing campaigns and as application entry points. The redirect path is an absolute path regular expression starting with `/' and the redirect destination can be relative to the current virtual host or an absolute URL including protocol and host. The regular expression matching variables $1..$9 can be used in the destination string.

Example: /sale to /eshop/products.asp?id=3342

Example: /sale to

Example: /wrong/(.*) to /correct/$1

If a virtual host is configured to accept HTTP as well as HTTPS connections it is possible to specify for which protocol the path redirect should be active. This can be used to redirect HTTP to HTTPS where desired. Such a redirect path pattern must be prefixed with the corresponding protocol tag [http] or [https] respectively. The following example redirects HTTP URLs to HTTPS URLs on the same virtual host.

Example: [http]/(.*) to https://%{HTTP_HOST}/$1

When you want to erase an existing query string, end the substitution string with just a question mark.

Example: /sale/ to /sale/?

Airlock Gateway does not support query string rewriting. Therefore the search pattern for the Redirect path does not have to match any query parameters. In case a query string is present in the source URL, the browser will send it also with the destination URL.

A redirect status code must be specified for each entry. These are the most important 2 codes:

  • 301 Moved Permanently - This and all future requests should be directed to the given URI.
  • 302 Found - This is an example of industry practice contradicting the standard. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, some Web applications and frameworks use the 302 status code as if it were the 303
  • 303 See Other - The response to the request can be found under another URI using a GET method. When received in response to a POST (or PUT/DELETE), it should be assumed that the server has received the data and the redirect should be issued with a separate GET message.

For a comprehensive list see here.