A.9 Known Rewriter Issues

A.9.1 Changes to the Rewriter

Viewing Changes to the Rewriter

For a listing of new features in the rewriter, see the rewriter.sam file located at sys:/etc/proxy/rewriter.sam.

Default Mime Type Changes

Text/plain is no longer a default mime type. If you want to have this mime type rewritten, you need to add it to the sys:etc\proxy\rewriter.cfg file in the [Mime Content-type] section.

The Internal Rewriter Command Has Been Removed

The [Internal Rewriter] command has been removed. In its place is a new command:

set accelerator <name> DisableRewriter=Yes|No

This setting is exported to the .nas file.

A.9.2 Rewriting Fails on a Page with Numerous HREFs

Although the rewriting failure occurs when downloading large amounts of data from the accelerated Web server, it's not the size or timeout of the page which is the issue. It is the number of links to be rewritten. There is a data size limit to the number of references that the rewriter can rewrite on a page.

The solution is to reduce the number of HREFs that need to be rewritten. If the problem is occurring because the rewriter is rewriting HTTP to HTTPS, you can solve this problem by disabling multi-homing for the Web server and by rewriting the Web page to use relative links. This reduces the number of links that need to be rewritten. For more information, see TID 10101106, iChain 2.3 not rewriting Web data correctly.