Location Header Not Being Rewritten in iChain 2.2
Novell Cool Solutions: Tip
Digg This -
Posted: 18 Sep 2003
Version: iChain 2.2
For more information and updates to this solution, please see TID-10080451
If you're seeing this problem:
Location: header in a redirect not being rewritten like it was in iChain 2.1
Here's a solution:
- Make sure you are on a post-FCS (First Customer Ship) build of iChain.
- In iChain 2.1, the configuration below would rewrite the Location: header in a redirect to reflect a change from HTTP to HTTPS. (Note there is no Alternate Host Name being used). In iChain 2.2, the header is not rewritten to HTTPS unless the Alternate Host Name configuration is used.
set accelerator mail dnsname=mail02.myserver.com set accelerator mail loginpage= set accelerator mail alturl= set accelerator mail port=80 clear accelerator mail webserver add accelerator mail webserver=22.214.171.124 clear accelerator mail address add accelerator mail address=126.96.36.199 set accelerator mail webserverport=80 set accelerator mail sendxforwardedforheader=No set accelerator mail fillhostheadertype=ForwardReceivedHost set accelerator mail hostmismatcherror=No
Note that the accelerator's DNS name is the same as the DNS name sent in the Location: header by the Web Server.
If "mail02.myserver.com" is placed in the Alternate Host Name field then iChain 2.2 will correctly rewrite the Location: header to HTTPS.
The issue is resolved in IC22FP2A.EXE and later.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com