Configuring Html Rewriting; Understanding The Rewriting Process - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual
Access gateway guide
Hide thumbs
Also See for ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010:
- Manual (374 pages) ,
- User manual (58 pages) ,
- Manual (192 pages)
Table of Contents
Advertisement
9b Click the name of the teaming proxy service, then click the Protected Resources tab.
9c For each teaming protected resource, click the Identity Injection link, select the Identity
Injection policy, click Enable, then click OK.
9d Click OK.
9e To save the configuration changes, click Devices > Access Gateways, then click Update.
1.5 Configuring HTML Rewriting
Access Gateway configurations generally require HTML rewriting because the Web servers are not
aware that the Access Gateway machine is obfuscating their DNS names. URLs contained in their
pages must be checked to ensure that these references contain the DNS names that the client browser
understands. On the other end, the client browsers are not aware that the Access Gateway is
obfuscating the DNS names of the resources they are accessing. The URL requests coming from the
client browsers that use published DNS names must be rewritten to the DNS names that the Web
servers expect.
Figure 1-6
HTML Rewriting
Figure 1-6
Browsers
Request
<HTML>
Reply
<img src=http://www.novell.com/path/image1.jpg/>
</HTML>
The following sections describe the HTML rewriting process:
Section 1.5.1, "Understanding the Rewriting Process," on page 49
Section 1.5.2, "Specifying the DNS Names to Rewrite," on page 51
Section 1.5.3, "Defining the Requirements for the Rewriter Profile," on page 54
Section 1.5.4, "Configuring the HTML Rewriter and Profile," on page 61
Section 1.5.5, "Creating or Modifying a Rewriter Profile," on page 64
Section 1.5.6, "Disabling the Rewriter," on page 67
1.5.1 Understanding the Rewriting Process
The Access Gateway needs to rewrite URL references under the following conditions:
To ensure that URL references contain the proper scheme (HTTP or HTTPS).
If your Web servers and Access Gateway machines are behind a secure firewall, you might not
require SSL sessions between them, and only require SSL between the client browser and the
Access Gateway. For example, an HTML file being accessed through the Access Gateway for
the Web site
novell.com
. If the reverse proxy for
image1.jpg
illustrates these processes.
HTML Headers
GET /path HTTP/1.1
Host: www.novell.com
HTML Page: Source
might have a URL reference to
novell.com/path
Configuring the Access Gateway to Protect Web Resources
Access Gateway
novell.com/path
HTML Headers
GET HTTP/1.1
Host: data.com
HTML
Rewriter
HTML Page: Source
<HTML>
<img src=http://data.com/image1.jpg/>
</HTML>
http://novell.com/path/
is using SSL sessions between the
Web Server
data.com
49
Advertisement
Chapters
Table of Contents
Troubleshooting
