Re: [squid-users] Probably solved: Problem with swf streams from www.tv4play.se behind squid
On 11/03/2012 12:22 p.m., Peter Olsson wrote: On Sat, Mar 10, 2012 at 04:11:30PM +1300, Amos Jeffries wrote: On 10/03/2012 5:55 a.m., Peter Olsson wrote: I set forwarded_for off in squid.conf, and this seems to solve the problem. I haven't tried in our production squids yet, but a lab squid is working now. Perhapse this will help their technicians detect the problem. If changing that header fixed it for you then the issue is clearly something at their end in its processing. I've been noticing this on a few sites now. For my clients it seems to be web systems which break on IPv6 addresses in the HTTP headers. X-Forwarded-For included. SquirrelMail seems to be the common culprit with its send button handler being broken. So, are your clients contacting Squid from IPv6 addresses? No, just IPv4 behind the Squid servers. We run IPv6 on the outside of Squid, but I don't know if www.tv4play.se uses any IPv6 in their services. I discovered today that the production squids (3.1.16) require forwarded_for delete. The lab squid (3.2 latest as of yesterday) worked with forwarded_for off, but not the 3.1.16 version. Strange that it should differ, or is there some way that Squid 3.1 and 3.2 handles this header differently? They should behave the same. Off sends the value "unknown" in the header instead of your clients IP. Delete removes it entirely. So it could be something downstream of your production Squids which gets in there but not from the testing environment. Amos
Re: [squid-users] Probably solved: Problem with swf streams from www.tv4play.se behind squid
On Sat, Mar 10, 2012 at 04:11:30PM +1300, Amos Jeffries wrote: > On 10/03/2012 5:55 a.m., Peter Olsson wrote: > > I set forwarded_for off in squid.conf, and this seems to > > solve the problem. I haven't tried in our production squids > > yet, but a lab squid is working now. > > Perhapse this will help their technicians detect the problem. If > changing that header fixed it for you then the issue is clearly > something at their end in its processing. > > I've been noticing this on a few sites now. For my clients it seems to > be web systems which break on IPv6 addresses in the HTTP headers. > X-Forwarded-For included. SquirrelMail seems to be the common culprit > with its send button handler being broken. > > So, are your clients contacting Squid from IPv6 addresses? No, just IPv4 behind the Squid servers. We run IPv6 on the outside of Squid, but I don't know if www.tv4play.se uses any IPv6 in their services. I discovered today that the production squids (3.1.16) require forwarded_for delete. The lab squid (3.2 latest as of yesterday) worked with forwarded_for off, but not the 3.1.16 version. Strange that it should differ, or is there some way that Squid 3.1 and 3.2 handles this header differently? -- Peter Olssonp...@leissner.se
Re: [squid-users] Probably solved: Problem with swf streams from www.tv4play.se behind squid
On 10/03/2012 5:55 a.m., Peter Olsson wrote: I set forwarded_for off in squid.conf, and this seems to solve the problem. I haven't tried in our production squids yet, but a lab squid is working now. Perhapse this will help their technicians detect the problem. If changing that header fixed it for you then the issue is clearly something at their end in its processing. I've been noticing this on a few sites now. For my clients it seems to be web systems which break on IPv6 addresses in the HTTP headers. X-Forwarded-For included. SquirrelMail seems to be the common culprit with its send button handler being broken. So, are your clients contacting Squid from IPv6 addresses? Amos
[squid-users] Probably solved: Problem with swf streams from www.tv4play.se behind squid
I set forwarded_for off in squid.conf, and this seems to solve the problem. I haven't tried in our production squids yet, but a lab squid is working now. Peter Olsson On Fri, Mar 09, 2012 at 03:46:19PM +0100, Peter Olsson wrote: > Sorry, forgot to mention that these streams work fine > through a Microsoft TMG proxy at the same network > position as one of our squid servers, so there is no > network problem. And I also should mention that we run > squid in proxy mode with clients configured either through > wpad or with a static proxy server. No transparency. > > Peter Olsson > > On Fri, Mar 09, 2012 at 03:24:45PM +0100, Peter Olsson wrote: > > Hello! > > > > We can't access swf streams from www.tv4play.se > > behind squid since about a month ago. Earlier we > > could at least play some of them, but now it seems > > that none of them work through squid. We haven't > > changed anything in the squid version or squid > > configuration that would cause this. We have > > contacted their support, but they see no problems > > on their side. > > > > I'm debugging the problem now (with ALL,9), but the > > size of the debug is enormous so it's hard to find > > anything relevant in there. Is there some debug setting > > I should rather use instead of ALL,9, to be able to > > locate the problem more easily? > > > > Our current squid version is 3.1, and I have tried > > both with 3.1.16 and 3.1.19. We run squid in FreeBSD. > > I have tried running squid both with and without > > caching active, same problem. > > I will try squid 2.7 later. > > > > Does anyone know of any problems with swf through squid, > > either in general or specifically from www.tv4play.se? > > (These streams are only available from Sweden, so they > > are unfortunately not available for general testing.) > > > > Thanks! > > > > -- > > Peter Olssonp...@leissner.se
