Environment
Novell Access Manager 3.1 Linux Access Gateway Service Service Pack
4
Situation
Purpose:
Protect and accelerate the Outlook Web Access 2003 (OWA 2003) application with Novell Access Manager 3.1.4 using the Access Gateway Service (MAG) on SLES 11 SP1.
Symptoms:
When accessing a mailbox having hundreds of emails in the inbox folder, and using the top-right corner arrows to browse back and forth across the different pages, suddenly the pages starts to be displayed garbled and with the actual page design completely screwed up.
Protect and accelerate the Outlook Web Access 2003 (OWA 2003) application with Novell Access Manager 3.1.4 using the Access Gateway Service (MAG) on SLES 11 SP1.
Symptoms:
When accessing a mailbox having hundreds of emails in the inbox folder, and using the top-right corner arrows to browse back and forth across the different pages, suddenly the pages starts to be displayed garbled and with the actual page design completely screwed up.
Resolution
The issue has been fixed in NAM 3.1 SP5.
Workarounds:
The issue occurs only if the option "Forward received host name" is selected in the Host Header field under the Web Server Tab in the proxy service configuration, and when the HTML rewriter is enabled. Both the following configuration change will clear the issue:
1) Have the MAG to send the real back-end web server host name, instead of forwarding the received host name form the browser. This can be done selecting "Web Server Host Name" and specifying the real back-end web server host name under the Web Server Tab in the proxy service configuration;
2) Disable the rewriter for the proxy service unchecking the"Enable HTML Rewriting" option under the HTML Rewriting tab under the proxy service configuration;
Workaround option 1 is the best practice suggested configuration.
Workarounds:
The issue occurs only if the option "Forward received host name" is selected in the Host Header field under the Web Server Tab in the proxy service configuration, and when the HTML rewriter is enabled. Both the following configuration change will clear the issue:
1) Have the MAG to send the real back-end web server host name, instead of forwarding the received host name form the browser. This can be done selecting "Web Server Host Name" and specifying the real back-end web server host name under the Web Server Tab in the proxy service configuration;
2) Disable the rewriter for the proxy service unchecking the"Enable HTML Rewriting" option under the HTML Rewriting tab under the proxy service configuration;
Workaround option 1 is the best practice suggested configuration.