Troubleshooting Crashes And Hangs - Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual

Web server host name: www.proxy91.com:8181
Web server connect port: 8080 (HTTP)
Published DNS name: www.lag.com
Listening Port: 443
Then:
The host header from Access Gateway to the Web server is rewritten as
www.proxy91.com:8181
If a page has URLs, the URLs are rewritten as follows:
http://www.proxy91.com:8181
https://www.proxy91.com:8181
The following URLs are not rewritten unless you add additional DNS names:
http://www.proxy91.com:8080
https://www.proxy91.com:8080
http://www.proxy91.com
https://www.proxy91.com
Scenario 2: Web Server Host Name without a Port Number
In this scenario, the Access Gateway rewrites URLs and host headers based on the configured Web
server host name.
For example, if your configuration looks similar to the following:
Web server host name: www.proxy91.com
Web server connect port: 8080 (HTTP)
Published DNS name: www.lag.com
Listening Port: 443
Then:
The host header from Access Gateway to the Web server is rewritten as
If a page has URLs, the URLs are rewritten as follows:
http://www.proxy91.com:8080
The following URLs are not rewritten unless you add additional DNS names:
https://www.proxy91.com:8080
http://www.proxy91.com:8181
https://www.proxy91.com:8181
http://www.proxy91.com
https://www.proxy91.com

7.6 Troubleshooting Crashes and Hangs

Section 7.6.1, "Enable the Access Gateway Monitor Service for the Core Dump Logic to Work
Correctly," on page 228
Section 7.6.2, "The Access Gateway Hangs When the Audit Server Comes Back Online," on
page 228
Section 7.6.3, "The Access Gateway Crashes When Log Files Are Removed," on page 229
Section 7.6.4, "Troubleshooting a Failed Access Gateway Configuration," on page 229
is rewritten as
https://www.lag.com
is rewritten as
https://www.lag.com
is rewritten as
https://www.lag.com
Troubleshooting the Access Gateway Appliance 227
.
www.proxy91.com