Thank you so much Eric and Tom.
We do not use warn-date in the response header. I added that. Still header
'Warning' missing.
HTTP/1.1 200 OK
Date: Fri, 07 Sep 2012 06:49:39 GMT
Server: Apache-Coyote/1.1
Accept: application/json
Content-Length: 468
Content-Type: application/json
warn-date:
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.
On Thu, Sep 6, 2012 at 6:59 AM, Anoop L anpl1...@gmail.com 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
On Thu, Sep 6, 2012 at 12:27 PM, Eric Covener cove...@gmail.com wrote:
On Thu, Sep 6, 2012 at 6:59 AM, Anoop L anpl1...@gmail.com 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
