Adding an HTTP/HTTPS Request Filter

Configure HTTP/HTTPS header fields that you use to filter certain types of outbound web traffic.

1. On the Secure Access Resources screen, click the HTTP/HTTPS Request Filters tab and then click Add.

   The HTTP/HTTPS Request Filter Settings screen appears.

2. Specify a name for the filter and add a description.
3. Select one or more request methods to match the filter.

   Table 1. Supported request methods

   Method	Description
   GET	Requests a representation of the specified resource.
   POST	Submits data to be processed (e.g., from an HTML form) to the identified resource. The data is included in the body of the request. This may result in the creation of a new resource or the updates of existing resources or both.
   PUT	Uploads a representation of the specified resource.
   HEAD	Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content.
   DELETE	Deletes the specified resource.

4. Specify the request URLs to match the filter.

   You can specify URL hosts and/or URL paths. Separate multiple entries by comma (,).

   • Select Any specified URL host name or IP address, and type the host name or IP address (including port number, if any) as part of the URL.

   • Select Any specified URL path, and type the path part of the URL. Do not start the path with the '/' or include the '?' of the query.

   The request URL supports both the (?) and (*) wildcard characters. ? matches any single character while * matches any number of any characters. For example,

   URL host name or IP address	URL path
   www.example.com matches www.example.com only.	example.com/news.htm matches example.com/news.htm only.
   www.example.c? matches www.example.co but not www.example.com.	example.com/news?.htm matches example.com/news1.htm but not example.com/news11.htm.
   *.example.com matches jp.example.com and us.example.com.	To match all URLs with the path including news, type *news*.

5. Specify the header fields and corresponding values to match the filter.
   1. Click Add.
   2. Specify the header field name under Header.

      The field name must comply with the HTTP naming standards, for example, User-Agent

   3. Select the operation from the drop-down list and type the values to be used in Value.

      This supports both string-value matching and integer-value comparison:

      • CONTAINS / NOT CONTAINS: Means the header field value contains or does not contain the keywords using a simple string comparison. Add multiple keywords with an OR relation by pressing Enter.

        Wildcard characters (?) and (*) are supported. In this syntax, to treat a wildcard character as a literal character, add an escape character, which is the backslash \, in front of the wildcard character. For example, if you want * to match just *, type \*.

      • =, ≠, ≥, ≤: Means integer-value comparison.

      • EXISTS / NOT EXISTS: Means whether the request includes or does not include the defined header.

   The web traffic is matched by one filter only if all the defined scopes are matched, which means there is an AND relation among Request method, Request URLs, and Header fields.

6. Click Save.

   You can add this filter in internet access rules as necessary.