URI - Match (Wildcards)

What can I do here?

Use this window to configure how a connection is matched to a Resource in a rule. If a connection matches the source and destination of the rule and the match parameters of the Resource, then both the Action in the Rule and the Action in the Resource are applied.

URI Wildcards Options

Schemes

• Select the URI Schemes to which this resource applies. It is only relevant when the Security Gateway is defined as a proxy for these protocols in the browser of the clients initiating the connection.
• You can specify another scheme in the Other field. You can use wildcards. If you use *, all schemes are allowed -including the schemes that are not selected.

Methods

• The GET method is used when you request a particular page (or elements on a page). It retrieves whatever information (in the form of an entity) is identified by the URI. It. If the URI refers to a data-producing process, it is the produced data, which is returned as the entity in the response and not the source text of the process, unless that text happens to be the output of the process.
• The POST method is used when sending data to a web site (filling out forms, for example). The actual function performed by the POST method is determined by the server and is usually dependent on the URI.
• The HEAD method is identical to GET except that the server does not return any Entity-Body in the response. It is usually used by caching servers and web browsers to determine whether or not an element has changed, in order to decide whether or not to download the element. It is also used for testing hypertext links for validity and accessibility.
• The PUT method is a less commonly used method for uploading files via HTTP (ftp using a browser).

  You can specify another method in the Other field. You can use wildcards. If you specify *, all methods are allowed, including the methods that are not selected.

Methods

The Host, Path and Query parameters break the URI into filterable components. For example

• Host: http://www.elvis.com - The functionality of the Host parameter depends on the DNS setup of the addressed server. For the host, only the IP address or the full DNS name should be used, (For example: 191.81.23.* or server.{paris,london}.com, but not {paris,london}). For expressions using a host name and port number, the port number must be explicitly specified, for example, the expression paris* matches requests on any port. It is recommended to restrict requests to a known HTTP server (for example, *.paris:80, or paris:80).
• Path: /alive/qc.html - For the Path, name matching is based on appending the file name in the request to the current working directory (unless the file name is already a full path name) and comparing the result to the path specified in the Resource definition.

  The file path name must include the directory separator character "/". For example, the request "/myfile" is matched to "/<current directory>/myfile". If the Resource path name specifies only "myfile", then the request will not be matched.

  When using wildcard characters for the Path, you must specify either the full path name, or use the directory separator in the wildcard expression. For example, the path name "*/myfile" will match "myfile" in all possible directories.

  Path includes the file name (which can include wildcard characters). For example: "/boys/fred/*" includes all the files in the /boys/fred/ directory, and "/boys/fred/" does not include any of the files in the /boys/fred/ directory. If /boys/fred were a file, it would be included in "/boys/fred/".

• Query - are the parameters that are sent to the URI when it is accessed.