Re: spotify blocked by squid

[Jonathan Filogna <jonathan.filogna@xxxxxxxxxxxx>]

Ty Amos.

one more question

if i run apt-get install squid3 on my debian server, i must change some lines like http_body_reply. But i can conserve my old squid.conf right?

I meant, how can i upgrade succesfully?
 should i start the installation from scratch?

This server's almost on production but this bug is a real pain.

Jonathan.

2015-06-10 15:02 GMT-03:00 Amos Jeffries <squid3@xxxxxxxxxxxxx>:

On 11/06/2015 5:39 a.m., Jonathan Filogna wrote:
> Hi all, it's me  again, just a simple question
>
> I've configured an squid 2.7 with ntlm auth and i want to let some AD users
> to listen spotify
>
> My problem is that spotify streaming is being blocked by squid to this
> group and idk why. Maybe another syntax problem?

Some possibilities:

* 2.7 has an old bug where CONNECT requests could drop the first few
bytes of a connection if they were received in the same packets as the
HTTP message itself. Modern uses of port 443 depends on that case working.

* NTLM severely violates many requirements of HTTP. The only way for it
to have half a chance of working with CONNECT is "auth_param ntlm
keep_alive off"

* 504 means the connection to upstream timed out. Could be both of the
above happening at once. So what should go to the server first didnt get
sent, nothing comes back as server waits, then


PS. Squid-2.7 and even NTLM are both more than 5 years since they
stopped receiving support. Please upgrade. The version difference to 3.5
is so great now that it may involve some time/pain but is well worth it.

Amos

_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users

--

Jonathan Filogna

It Senior

Tasso SRL
4702 1910

_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users