|
Problem(Abstract) |
There are some URLs in HTML pages that should not be
rewritten by the JunctionRewrite plug-in, such as the URLs that already
have the junction prefix. Also, there might be some URL prefixes that need
to be replaced with other prefixes.
Two new directives for the JunctionRewrite plug-in are introduced to
handle these cases. |
|
|
|
Cause |
Two new directives are introduced to avoid the junction
plug-in rewriting certain URLs. The new directives have no effect on the
proxy if JunctionRewrite plug-in is disabled. |
|
|
Resolving the
problem |
With Caching Proxy V5.0.2 (Edge Components) and Caching
Proxy V4.0.2 (Edge Server v2.0.2), the following two new Caching Proxy
directives are introduced to control the JunctionRewrite plug-in:
JunctionSkipUrlPrefix url-pattern
With this directive, the JunctionRewrite plug-in skips rewriting the URLs
that match the url-pattern. Normally the directive is used to skip
the URLs that already include a prefix.
For example:
If the URL is:
/server1/notes.nsf
and you set the directive to:
JunctionSkipUrlPrefix /server1/*
instead of rewriting the URL to:
/server1/server1/notes.nsf
the JunctionRewrite plug-in skips rewriting the URL, and the URL
remains the same: /server1/notes.nsf.
Note: NoJunctionUrlPrefix and JunctionSkipUrlPrefix are
synonymous.
JunctionReplaceUrlPrefix url-pattern1 url-pattern2
With this directive, the JunctionRewrite plug-in replaces
url-pattern1 with url-pattern2 instead of inserting a prefix
at the beginning of the URL.
For example:
If the URL is:
/server1.internaldomain.com/notes.nsf
and you set the directive to:
JunctionReplaceUrlPrefix /server1.internaldomain.com/* /server1/*
the JunctionRewrite plug-in changes the URL to:
/server1/notes.nsf |
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Application Servers |
WebSphere Edge Server |
Caching Proxy |
Multi-Platform |
Edge Server 2.0.x |
|
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|