Reverse Proxy Header Munging

• From: John C. Mallery <jcma@ai.mit.edu>
• Date: Sun, 12 Oct 2003 23:36:46 -0400
• To: ietf-http-wg@w3.org
• Message-Id: <p05210611bbafcc4926e2@[10.0.1.3]>

I'd like to here what people think about the behavior of the current Apache reverse proxy, which rewrites the host header and adds the three x-forwarded-* headers.

What is the status of these x-forwarded-* headers?

Are there some specs to which implementations should adhere, or is this an Apache ideosyncracy
(bug)?

------------
Client Headers for 127.0.0.1 (HTTP/1.1)

:HOST =>  "127.0.0.1" 8000
:ACCEPT => (:* :*)
:ACCEPT-LANGUAGE => (:EN-US . 1) (:JA . 0.33) (:EN . 0.67)
:IF-MODIFIED-SINCE => 3187296000
:USER-AGENT => "Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/85.7 (KHTML, like Gecko) Safari/85.5"
:X-FORWARDED-FOR => "10.1.1.3"
:X-FORWARDED-HOST => "my.host.com:443"
:X-FORWARDED-SERVER => "localhost.localdomain"
:CONNECTION => :CLOSE

Received on Sunday, 12 October 2003 23:42:14 UTC