Alex Rousskov <rousskov <at> measurement-factory.com> writes: > > On 12/30/2015 02:24 PM, Aashima wrote: > > > So it is like client -> Squid -> APP and return > > If App return Transfer-Encoding header to Squid, Squid removes that response > > header and forwards rest to Client. > > > > Am not getting why it is removing that header ? Couldnt find any posts > > also on any discussion group or blog. > > Transfer-Encoding is a standard HTTP hop-by-hop header. Hop-by-hop > headers are meant for the immediate recipient (Squid in your case), > rather than the final or "end" recipient (Client in your case). Squid > must not forward hop-by-hop headers (but may add them as needed, which > may look like forwarding to an outside observer). > > If you describe the actual problem you are having (in addition to this > technical detail), somebody on this list might be able to guide you > towards a solution. > > Good luck, > > Alex. > > _______________________________________________ > squid-users mailing list > squid-users <at> lists.squid-cache.org > http://lists.squid-cache.org/listinfo/squid-users > Hey Alex, Thanks for responding so quickly on that yesterday. This really helped me in reaching to one point for figuring out the real problem. So in my case, figured out when squid receives request header "Connection: close" , it strips of Transfer Encoding header from response. But if it does not receive Connection header it wil send back TE header. So I am left with 2 questions now. - Why does squid behave like that? - Second, so in my case HA Proxy is sending those headers to squid. Since Connection is also hop by hop header , why is HAProxy adding that header to request headers. Thanks Aashima _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
