|
The server doesn't define any "content-encoding". This is the original
server reply, tcpdumped:
HTTP/1.1 200 OK
Set-Cookie: ACE-STICKY=R1291873686; path=/; expires=Mon,
26-Dec-2016
23:51:26 GMT
Date: Mon, 26 Dec 2016 19:36:06 GMT
Accept-Ranges: bytes
Content-Length: 152264
Content-Type: text/css; charset=UTF-8
X-Powered-By: Servlet/3.0 JSP/2.2
Cache-Control: max-age=0, no-cache, no-store, must-revalidate
Pragma: no-cache
Content-Language: en
Set-Cookie:
JSESSIONID=DCLCYhxGPHvpfnPNsPv51cGkS55GPqB4b3xJsybLgLJpyqPZZhNW!-162452808;
path=/; HttpOnly
--
Best Regards,
Heiler Bemerguy
Network Manager - CINBESA
55 91 98151-4894/3184-1751
Em 26/12/2016 21:07, Alex Rousskov
escreveu:
On December 26, 2016 10:11:55 AM Heiler Bemerguy
wrote:
*Accept-Encoding: none*
*Content-Encoding: gzip*
These are end-to-end headers. Squid does not modify or add them
(unless you tell it to do that).
The origin server does not honor the bogus "none" content coding
requested by the client.
HTH,
Alex.
|
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
