Linux Access Gateway 302 redirects not rewriting Host header details when 'Forward Received Host Name' enabled

  • 7000173
  • 22-Apr-2008
  • 26-Apr-2012


Novell Access Management 3 Linux Access Gateway
Novell Access Management 3 Support Pack 2 applied


Linux Access Gateway with a path based multihomed (pbmh) resource (e.g.pbmh under mylag proxy service) that accelerates a Web server listening out on non standard port (801). The host header option is setup to forward recieved host header. When the web server, listening on TCP 801, generates a 302 redirect, we see the following:

GET /formfill/phpinfo.php HTTP/1.1
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
application/x-shockwave-flash, */*
Accept-Language: en-IE
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)
Connection: Keep-Alive

HTTP/1.1 302 Found
Date: Fri, 25 Jan 2008 11:02:49 GMT
Server: Apache/2.2.3 (Linux/SUSE)
Content-Type: text/html; charset=iso-8859-1
Content-Length: 309
ExtraHdr: 70
Cache-Control: no-store
Cache-Control: no-cache
Via: 1.1 (Access Gateway 3.0.2-56)

The 'Location:' should be rewritten
to Location: but it's not rewriting the
TCP port correctly. When we change the Host header and explicitly specify the
one we need ( instead of forwarding the received hostname (which
is also, it works fine.


If you enable the Forward Received Host Name option on your path-based
multi-homing service and your Web server is configured to use a different port,
you need to add the DNS name with the port to the the Additional DNS Name

For example, if the public DNS name of the proxy service is, the
path for the path-based multi-homing service is /sales, and the Web server port
is 801, the following DNS name needs to be added to the Additional DNS Name
List of the /sales service: