Understanding Url Path Matching; Using A Query String In The Url Path - Novell ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE Manual

1.4.2 Understanding URL Path Matching

The URL path determines which protected resource is used for a user request. Suppose you create
one protected resource with the following URL paths:
/*
/test/*
/test/
You create a second protected resource with the following path:
/test/*.php
Users then send the following paths in their access requests:
/test/
/test/1/2/3/file.php
/file.php
/test/file.php
/test/file.php?param1=1234
The first three requests ( , , and ) match the first
/test/ /test/1/2/3/file.php /file.ph
protected resource, and the last two requests ( and
/test/file.php
/ ) match the second protected resource.
test/file.php?param1=1234
You then add the following URL path to the first protected resource:
/test/?
This URL path in the first protected resource causes all the requests to match the first protected
resource, and the second protected resource is ignored. The ? wildcard, which matches all content in
the current directory, takes precedence over the more specific wildcard (*.php).
URL paths are case insensitive. If your Web server has two paths
( and ), a URL path of matches both.
/public/current /public/Current /public/current

1.4.3 Using a Query String in the URL Path

You can specify a query string in the URL path of a protected resource. For example:
URL path:
/test/index.html?test=test
When the requested URL has a query string, the Access Gateway searches for a protected resource
with a matching URL path and query string. If it can't find a match, the request returns a
resource
error.
not found
The Access Gateway Appliance allows you to configure the URL matching process so that it ignores
the query string in the URL path.
On the Access Gateway Appliance, you can remove the query string from the URL path or you can
create the following touch file:
/var/novell/.prWithOutQuestionMark
You need to then restart the Access Gateway Appliance to activate the touch file. When this touch
file is used, the Access Gateway Appliance ignores the query string and uses just the path to find a
match.
Configuring the Access Gateway to Protect Web Resources 23