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
work
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.
>
Hey Ryan,
I noticed that you are using a windows version of squid and ontop of
that a 2.X version.
Technically this version is not supported anymore by the squid-cache
project and from the settings either you are running a very old machine
or something else not really known to me.
It's hard to
Hi this is not an SSL site.
Here is the config (I have stripped out the ACL's)
# WELCOME TO SQUID 2# --
# NETWORK OPTIONS#
-
# OPTIONS WHICH AFFECT THE NEIGHBOR SELECTION ALGORITHM#
-
Can you send me or the list your squid.conf?
Also are you using SSl-BUMP? is this a https site?
Eliezer
On 01/03/2016 00:36, Ryan Slick wrote:
Hi Guys,
So here is an issue I am having,
there is a external website some of our users need to access. When
accessing via the Squid proxy, the site t
Hi Guys,
So here is an issue I am having,
there is a external website some of our users need to access. When accessing
via the Squid proxy, the site throws this error on the page:
iisnode encountered anerror when processing the request.
HRESULT: 0xb
HTTP status: 500
HTTP reason: InternalServ