Hello Amos We have a windows internal DNS server, I used those DNS servers to resolve my IP's I changed the dns_nameserver to my ISP dns servers, and the problem went away, loaded ads and the complete page. I tried this morning eary before most of the staff came in to replicate the problem, but to no avail. I will try again when the office is busy again. Will send you the logs asap. Regards, Dawie Pretorius wrote: > Hello Amos > > The problem was DNS, my apologies for wasting your time. ? how so? > > "Meanwhile can you add debug_options 11,9 to your squid.conf and run a > test please. The resulting cache.log file will have a lot of garbage, > but amongst that some messages about what headers were received back and > what happened in the processing" > > I can still run this for you and send you the output? I think yes. I'm intrigued how that came out of a DNS problem. I'd expect connection or DNs errors to show up. Amos. > > Again thanks! :D > > Regards > Dawie > > > > > Dawie Pretorius wrote: >> Hello Amos >> >> Thanks for coming back to me, >> >> I upgraded to squid Beta Squid 3.1.0.15, /var/log/squid/access.log now has this error: >> >> 1263975667.799 92 172.16.9.158 TCP_MISS/302 1361 GET http://googleads.g.doubleclick.net/pagead/ads? Xxxxxxxxxxxxxxx DIRECT/72.14.204.154 text/html > <snip repeats> > > 302 with that content? Thats a not-modified response from the server. > >> Here is the cache.log >> > <snip> > > Not even a hint of problems. > >> Here is the page that I get back from the browser: >> >> ERROR >> The requested URL could not be retrieved >> >> Invalid Response error was encountered while trying to process the request: >> >> GET /pagead/ads?client=ca-pub-7266757337600734&format=336x280_as&output=html&h=280&w=336&lmt=1199983288&channel=5629109116%2B6771450170%2B2275486144&ad_type=text_image&alternate_ad_url=http%3A%2F%2Fwww.mail-archive.com%2Fblank.png&color_bg=FFFFFF&color_border=FFFFFF&color_link=006792&color_text=000000&color_url=006792&flash=10.0.32&url=http%3A%2F%2Fwww.mail-archive.com%2Fsquid-users%40squid-cache.org%2Fmsg51945.html&dt=1263975312151&correlator=1263975312153&frm=0&ga_vid=866186005.1263975312&ga_sid=1263975312&ga_hid=523487483&ga_fc=0&u_tz=120&u_his=1&u_java=0&u_h=1024&u_w=1280&u_ah=1024&u_aw=1280&u_cd=32&u_nplug=8&u_nmime=24&biw=1280&bih=862&ref=http%3A%2F%2Fwww.google.co.za%2Furl%3Fsa%3Dt%26source%3Dweb%26ct%3Dres%26cd%3D1%26ved%3D0CAcQFjAA%26url%3Dhttp%253A%252F%252Fwww.mail-archive.com%252Fsquid-users%2540squid-cache.org%252Fmsg51945.html%26rct%3Dj%26q%3DTCP_MISS%252F502%2Bsquid%26ei%3DV7tWS7yqK4S9lAeP-dz3Aw%26usg%3DAFQjCNGZUlUd4iFBeTKD1KXThtG3w31cLQ&fu=0&ifi=1&dtd=3 1 > &xpc=WgwVHxdvOD&p=http%3A//www.mail-archive.com HTTP/1.1 >> Host: googleads.g.doubleclick.net >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) >> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 >> Accept-Language: en-gb,en;q=0.5 >> Accept-Encoding: gzip,deflate >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 >> Keep-Alive: 300 >> Proxy-Connection: keep-alive >> Referer: http://www.mail-archive.com/squid-users@xxxxxxxxxxxxxxx/msg51945.html >> Cookie: test_cookie=CheckForPermission; id=22ac216e0800009b||t=1263975130|et=730|cs=mr_u8kmr >> Proxy-Authorization: NTLM TlRMTVNTUAADAAAAGAAYAIgAAAAYABgAoAAAABAAEABIAAAAHgAeAFgAAAASABIAdgAAAAAAAAC4AAAABYKIogUBKAoAAAAPVABCAEEARgBSAEkAQwBBAGQAYQB3AGkAZQAuAHAAcgBlAHQAbwByAGkAdQBzAEQAQQBXAEkARQBQAC0ATABUACncpJrZCLgCAAAAAAAAAAAAAAAAAAAAAOpZoYZfwwoauJ0u1F2AVKjAm/c35ZRlVw== >> >> The HTTP Response message received from the contacted server could not be understood or was otherwise malformed. Please contact the site operator. >> >> Your cache administrator may be able to provide you with more details about the exact nature of the problem if needed. >> >> Your cache administrator is webmaster. >> >> Generated Wed, 20 Jan 2010 08:19:13 GMT by XXXXXXXXXXXXX (squid/3.1.0.15) >> >> Is this something in squid causing this? Or is this something on the network? > > If you are not getting this errors, then this has to be something on > my side? > > I'm not sure at this point. > There is no indication yet what error Squid thinks exists in the reply. > > Comparing the two error pages it looks like 3.0 was barfing on the > Cookie. 3.1 seems to find something else. > > I'm adding some debug to Squid permanently that should help track these > down in future. > > Meanwhile can you add debug_options 11,9 to your squid.conf and run a > test please. The resulting cache.log file will have a lot of garbage, > but amongst that some messages about what headers were received back and > what happened in the processing. > > Amos -- Please be using Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21 Current Beta Squid 3.1.0.15 Note: Privileged/Confidential information may be contained in this message and may be subject to legal privilege. Access to this e-mail by anyone other than the intended is unauthorised. If you are not the intended recipient (or responsible for delivery of the message to such person), you may not use, copy, distribute or deliver to anyone this message (or any part of its contents ) or take any action in reliance on it. All reasonable precautions have been taken to ensure no viruses are present in this e-mail. As our company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments we recommend that you subject these to your virus checking procedures prior to use. The views, opinions, conclusions and other information expressed in this electronic mail are not given or endorsed by the company unless otherwise indicated by an authorized representative independent of this message.
