Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (nike.apache.org: local policy)
References: <33468056.post@talk.nabble.com>
In-Reply-To: <33468056.post@talk.nabble.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
Message-Id: <74DA27C5-6A05-4D65-880D-A07F12D35B08@webthing.com>
Content-Transfer-Encoding: 7bit
From: Nick Kew <nick@webthing.com>
Date: Fri, 9 Mar 2012 10:46:06 +0000
To: users@httpd.apache.org
Subject: Re: [users@httpd] mod_proxy removing/filtering origin response
 headers


On 8 Mar 2012, at 21:35, TomFennelly wrote:

> 
> Hi there.
> 
> I have a reverse proxy configured, but mod_proxy seems to be removing some
> of the response headers that were sent from the origin server.  I need the
> ones in question to be passed back to the client (websocket connection
> upgrade handshake headers).  Is there a way of configuring this?  I can't
> find it anywhere.

You're up against a mismatch of what websockets expect and what HTTP defines.
mod_proxy_http implements HTTP, and can't be held responsible for other
protocols.

Assuming(?) no complexities beyond the headers, it would be straightforward
to hack mod_proxy_http to provide that option (note: NOT do that by default).
It just needs someone to sit down with the websockets spec and go through
the relevant contradictions with HTTP.

You could also question why the websockets folks went and abused hop-by-hop
headers when they could instead have done what HTTP provides for and
created extension headers to meet their needs without breaking anything!

-- 
Nick Kew

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org