Re: [squid-users] Problem at loading advert with Squid 2.7 & 3.1

 On Tue, 27 Dec 2011 11:21:37 +0100, feralert wrote:
> On Tue, Dec 27, 2011 at 10:37 AM, Amos Jeffries
> <squid3_at_treenet.co.nz> wrote:
>> On Mon, 26 Dec 2011 18:21:25 +0100, feralert wrote:
>>>
>>> Dear all,
>>>
>>> Squid is not loading an advert in a web page frame which loads fine
>>> when using a direct connection to the internet.
>>> The versions used are 2.7.STABLE9-2.1 and 3.1.6-1.2 both in a
>>> debian
>>> squezze with default configuration)
>>>
>>> The url the frame tries to load is:
>>>
>>>
>>>
>>>
>>> http://frame.cool.com/ad-frame/#&ad_wrap=ad-1&ad_url=http://ad.doubleclick.net/adj/site011.opus/home;Slot=Leaderboard;Pos=Top;Page=home;LoggedIn=No;tile=1;sz=728x90;&ad_timestamp=13249166700149
>>>
>>>
>>> In squids log file I only see a line for
>>> 'http://frame.cool.com/ad-frame/':
>>>
>>> 1324916528.019   5405 192.168.5.237 TCP_REFRESH_MISS/200 445 GET
>>> http://frame.cool.com/ad-frame/ - DIRECT/67.228.247.179 text/html
>>>
>>> But no sight of a
>>> ''http://ad.doubleclick.net/adj/site011.opus/hom"e
>>> request.
>>>
>>>
>>> If I load the page in my computer (with a direct connection to the
>>> internet) and watch http traffic with the "http fox" firefox
>>> extension, I can see both requests.
>>>
>
> Hi Amos and all,
>
>>
>> The browser appears to have a bug. You demonstrated only one URL.
>> "http://frame.cool.com/ad-frame/"
>
> I forgot to mention that I tried loading the page with firefox,
> chromium and IE and got the same results with all of them. And all of
> them are able to load the page fine when using a direct connection to
> the internet (without proxy).
>
>>
>> The '#' character is reserved for browser internal use. On a page
>> view like
>> this the browsers move the top of the visible display area down to
>> the part
>> of the page labeled
>>
>> "&ad_wrap=ad-1&ad_url=http://ad.doubleclick.net/adj/site011.opus/home;Slot=Leaderboard;Pos=Top;Page=home;LoggedIn=No;tile=1;sz=728x90;&ad_timestamp=13249166700149".
>> That label is not itself a URL.
>>
>> So... there is no second URL to Squid, unless there is a completely
>> separate
>> lookup triggered by something else you did not mention.
>
> Even so, I see that my first message wasn't somehow displayed
> properly
> and might not be clear enough. Where it says 'But no sight of a ''"e
> request.', I meant to say: 'But no sight of a
> http://ad.doubleclick.net/adj/site011.opus/home request', meaning
> that
> there is a GET request for the first url but not for the second (as
> seen when not using squid but a direct connection to the internet).
>
> I have taken traces of the HTTP traffic with tcpdump, which I show
> below. The first one is using squid 2.7, which fails to load the ad
> and the second with the direct connection to the internet, which
> works
> flawlessly. As can be seen, when using squid, there is no data in the
> reply from the server, whereas there is some in the reply to the same
> request when using the direct connection, could the 'not requesting
> second url' error be due to this ??
>
>
> - Squid 2.7:
>
> Host: frame.cool.com
> User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20100101
> Firefox/10.0
> Accept:
> text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language: es-es,es;q=0.8,en-us;q=0.5,en;q=0.3
> Accept-Encoding: gzip, deflate
> Proxy-Connection: keep-alive
> Referer: http://www.cool.com/
> Cookie: cool_all=24042dc2a0e328135316d197a53f45e8;
> cool_l=%7B%22n%22%3A4%2C%22d%22%3A1%7D;
> manifest=%7B%22pth%22%3A%7B%22rpge%22%3A%22home%22%7D%7D;
> __qca=P0-613459998-1324917196001;
> __utma=215533653.1105349504.1324917196.1324917196.1324917196.1;
>
> __utmz=215533653.1324917196.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);
> __utmv=215533653.home
>
> HTTP/1.0 200 OK
> Server: nginx/1.0.4
> Content-Type: text/html; charset=UTF-8
> X-Powered-By: PHP/5.3.6
> Expires: Tue, 27 Dec 2011 16:22:04 GMT
> Last-Modified: Mon, 26 Dec 2011 16:22:04 GMT
> Cache-Control: public, max-age=86400
> Date: Mon, 26 Dec 2011 16:22:04 GMT
> X-Varnish: 1092645737
> Age: 6176
> Content-Length: 0
> X-Cache: HIT from coruscant
> X-Cache-Lookup: HIT from coruscant:3128
> Via: 1.1 varnish, 1.1 coruscant:3128 (squid/2.7.STABLE9)
> Connection: keep-alive
> Proxy-Connection: keep-alive
>

 The last response Squid got for that URL was cacheable for 24hrs and
 had no content. Squid is now serving that cached response until the 24hr
 storage time expires.

 Force a cache revalidation from the client (press Shift or Ctrl key
 while clicking the refresh/relaod browser button).

 Amos
Received on Tue Dec 27 2011 - 11:58:42 MST