Re: [squid-users] diff 2.5.STABLE5 to 2.7.STABLE4

On 15/04/11 01:39, alois blasbichler wrote:
> Hello list
>
> I have a strange behaviour with my squid ( 2.7.STABLE4) :
> When i open acertain website (site with webservices) with a browser all
> works fine.
> But wenn i open the same site with a special program i get an error and
> in the log of my squid i see only : TCP_MISS:none
> we configured : cache_peer x.x.x.x parent
> and on this parent no requests was send.
>
> The strange is installing for test an older squid (2.5.STABLE5):
> this sites with the special program is open fine and in the log of the
> squid i see : TCP_MISS:FIRST_UP_PARENT
>
> Now my question : is there changed a default setting in squid from
> version 2.5.STABLE5 to 2.7.STABLE4 that can cause this error ?
>
> I made also debugging - there are a lot of lines like below - if i
> should send more logs please say.
>
> Thank you and by
> luis
>
>
>
> #########################################
> 2011/04/07 12:28:50| 0x8c0d788 lookup for 41
> 2011/04/07 12:28:50| 0x8c0d788 lookup for 9
> 2011/04/07 12:28:50| 0x8c0d788 lookup for 41
> 2011/04/07 12:28:50| 0x8c0d788 lookup for 9
> 2011/04/07 12:28:50| 0x8c0d788 lookup for 25
> 2011/04/07 12:28:50| appending hdr: 0x8c0d788 += 0x87ec718
> 2011/04/07 12:28:50| created entry 0x8cdc108: 'Server: squid/2.7.STABLE4'
> 2011/04/07 12:28:50| 0x8c0d788 adding entry: 47 at 0
> 2011/04/07 12:28:50| created entry 0x8991b20: 'Date: Thu, 07 Apr 2011
> 10:28:50 GMT'
> 2011/04/07 12:28:50| 0x8c0d788 adding entry: 23 at 1
> 2011/04/07 12:28:50| created entry 0x84c6438: 'Content-Type: text/html'
> 2011/04/07 12:28:50| 0x8c0d788 adding entry: 18 at 2
> 2011/04/07 12:28:50| created entry 0x8ea5f60: 'Content-Length: 1701'
> 2011/04/07 12:28:50| 0x8c0d788 adding entry: 14 at 3
> 2011/04/07 12:28:50| created entry 0x89dca98: 'Expires: Thu, 07 Apr 2011
> 10:28:50 GMT'
> 2011/04/07 12:28:50| 0x8c0d788 adding entry: 25 at 4
> 2011/04/07 12:28:50| created entry 0x8707f98: 'X-Squid-Error:
> ERR_INVALID_REQ 0'
<snip>

Well that is the reply headers that Squid is sending back to your
special app.
  The problem is in the request headers it is sending to Squid.
Something is either broken in them or not understood by Squid.

cache.log may have earlier entries about the headers received and
processing them. But the easiest way is usually to grab a copy of the
TCP packets going into Squid and read the "TCP stream" report in wireshark.

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.12
   Beta testers wanted for 3.2.0.6