I have investigated the issue and it seems that the specific application
on the IIS 8.5 server cannot handle HTTP/1.0 with some Accept-Encoding
headers.
Specifically what is being used is: Accept-Encoding: gzip, deflate
and if I remove the gzip and defalte and replace it with xxx or yyy it
works fine. If one of these exists(and maybe others) with a HTTP/1.0
request to this specific application it will result in 500 Internal
error page.
My suggestion is that since the clients and the service requires
HTTP/1.1 is to try and upgrade the squid service in any way possible to
add support for HTTP/1.1.
If you have a specific environment feel free to share it with me
publicly or privately to see if there is a smooth upgrade path for your
environment.
Eliezer
On 01/03/2016 03:13, Amos Jeffries wrote:
On 1/03/2016 12:26 p.m., Eliezer Croitoru wrote:
>Hey Ryan,
>
>I noticed that you are using a windows version of squid and ontop of
>that a 2.X version.
And on top of that it has been patched with unknown extensions. So is
formally outside our ability to assist with support of this binary.
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
