192 Novell Access Manager 3.1 SP1 Access Gateway Guidenovdocx (en) 19 February 2010cat /proc/meminfo | grep MemTotal7.5 Rewriter Issues Section 7.5.1, “Discovering the Issue,” on page 192 Section 7.5.2, “Rewriting Fails on a Page with Numerous HREFs,” on page 192 Section 7.5.3, “Links Are Broken Because the Rewriter Sends the Request to the Wrong ProxyService,” on page 192 Section 7.5.4, “Reading Configuration Files,” on page 193 Section 7.5.5, “Rewriter Does Not Rewrite Content in Files with a Non-Default Extension,” onpage 193 Section 7.5.6, “Additional DNS Name Without a Scheme Is Not Rewritten,” on page 194 Section 7.5.7, “Rewriting a URL,” on page 1947.5.1 Discovering the IssueTo isolate a rewriter issue:1 Go to the Web server, access the page that is causing the rewriter problem, use view sourceoption of the browser, then copy the source to a text file.2 Access the page from Access Manager, view the source, and copy it to a text file.3 Use a diff tool to compare the differences between the two files.This should help you identify the URLs that need to be rewritten but aren’t being rewritten.7.5.2 Rewriting Fails on a Page with Numerous HREFsAlthough the rewriting failure occurs when downloading large amounts of data from a protectedWeb server, it is not the size or the timeout of the page that is the issue. It is the number of links to berewritten. The Access Gateway has a data size limit for the number of references that the rewritercan rewrite on a page.The solution is to reduce the number of HREFs on the page that need to be rewritten. If the problemis occurring because the rewriter is rewriting HTTP to HTTPS, you can solve this problem bydisabling multi-homing for the Web server and by rewriting the Web page to use relative links. Thisreduces the number of links that need to be rewritten.7.5.3 Links Are Broken Because the Rewriter Sends theRequest to the Wrong Proxy ServiceWhen links on the Web server are rewritten to the wrong proxy service, the reverse proxy and Webservers might have the following configuration: The initial request from the browser is to a path-based multi-homing proxy service. The reverse proxy is configured to service one or more path-based proxy services. The path-based proxy services are configured to Forward Received Host Name and to RemovePath on Fill. The Web servers protected by these path-based proxy services have links to each other.
