1. Manuals
  2. Brands
  3. Novell Manuals
  4. Gateway
  5. ACCESS MANAGER 3.1 SP1 - ADMINISTRATION
  6. Manual

Novell ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE Manual page 51

Access gateway guide
Hide thumbs Also See for ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE:
Table of Contents

Advertisement

All occurrences of the string DOG are replaced with CAT, regardless of whether it is the word
DOG or the word DOGMA. Only one replacement pass occurs. The rewritten CAT is not
replaced with COT.
Because string replacement is done in one pass, the string that matches first takes precedence.
Suppose you have listed the following search and replacement strings:
ABC
to be replaced with
BCDEF
to be replaced with
If the original string is ABCDEFGH, the replaced string is XYZDEFGH.
If two specified search strings match the data portion, the search string of longer length is used
for the replacement except for the case detailed above. Suppose you have listed the following
search and replacement strings:
ABC
to be replaced with
ABCDEF
to be replaced with
If the original string is ABCDEFGH, the replaced string is PQRSTUVWXYZGH.
Using $path to Rewrite Paths in JavaScript Methods or Variables
You can use the $path token to rewrite paths on a path-based multi-homing service that has the
Remove Path on Fill option enabled. This token is useful for Web applications that require a
dedicated Web server and are therefore installed in the root directory of the Web server. If you
protect this type of application with Access Manager using a path-based multi-homing proxy
service, your clients access the application with a URL that contains a /path value. The proxy service
uses the path to determine which Web server a request is sent to, and the path must be removed from
the URL before sending the request to the Web server.
The application responds to the requests. If it uses JavaScript methods or variables to generate paths
to resources, these paths are sent to client without prepending the path for the proxy service. When
the client tries to access the resource specified by the Web server path, the proxy service cannot
locate the resource because the multi-homing path is missing. The figure below illustrates this flow
with the rewriter adding the multi-homing path in the reply.
Rewriting with a Multi-homing Path
Figure 1-6
Browsers
HTML Page: Source
<HTML>
<a href="../inner/prices/pricelist.html" class="ulink">
</HTML>
XYZ
PQRSTUVWXYZ
XYZ
PQRSTUVWXYZ
Firewall
Access
Gateway
Request
novell.com
novell.com/inner
Reply
Rewriter
Configuring the Access Gateway to Protect Web Resources
Web Server
inner.com
HTML Page: Source
<HTML>
<a href="../prices/pricelist.html" class="ulink">
</HTML>
51

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE and is the answer not in the manual?

Related Manuals for Novell ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE

Related Products for Novell ACCESS MANAGER 3.1 SP1 - GATEWAY GUIDE

Table of Contents