Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

Location header not being rewritten in iChain 2.2

(Last modified: 17Sep2003)

This document (10080451) is provided subject to the disclaimer at the end of this document.


iChain 2.2


Location: header in a redirect not being rewritten like it was in iChain 2.1

javascript redirect not working in iChain 2.2


1)  Make sure you are on a post-FCS (First Customer Ship) build of iChain.

2) 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
set accelerator mail loginpage=
set accelerator mail alturl=
set accelerator mail port=80
clear accelerator mail webserver
add accelerator mail webserver=
clear accelerator mail address
add accelerator mail address=
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 "" is placed in the Alternate Host Name field then iChain 2.2 will correctly rewrite the Location: header to HTTPS.

A defect was submitted to engineering on this issue (4/15/03).   The issue is resolved in IC22FP2A.EXE and later.


The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10080451
  • Solution ID: NOVL87281
  • Creation Date: 21Feb2003
  • Modified Date: 17Sep2003
    • NovellConnectivity Products

Did this document solve your problem? Provide Feedback