On Thu, Sep 6, 2012 at 12:27 PM, Eric Covener <covener@xxxxxxxxx> wrote: > On Thu, Sep 6, 2012 at 6:59 AM, Anoop L <anpl1980@xxxxxxxxx> wrote: >> Hi All, >> >> We use HTTPD 2.2.17 with Mod_ssl and Mod_proxy in front of HA_proxy to >> terminate https. >> >> When the backend sends http header named 'Warning' HTTPD removes that from >> response sent to client. I tried adding a customer header value named >> 'Warning1' and client gets that value in response. Any idea why Apache >> filters 'Warning' header is it a bug or related to security. >> >> Any help would be appreciated. > > It looks like mod_proxy filters warnings that have a date in the > warning that doesn't match the backend Date: header. > As required by the RFC: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.46 (Final paragraph in that section) Cheers Tom --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|