On Mon, 18 Jan 2010 00:22:09 +0200, Arthur Titeica <arthur.titeica@xxxxxxxxx> wrote: > On 09.12.2009 03:43, Amos Jeffries wrote: >> On Tue, 08 Dec 2009 20:40:12 +0200, Arthur Titeica >> <arthur.titeica@xxxxxxxxx> wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On 06.12.2009 16:20, Arthur Titeica wrote: >>>> Hi, >>>> >>>> Recently I see lots of the following in my squid logs >>>> >>>> 1259130624.131 0 89.42.191.44 NONE/400 3172 GET >>>> >> (null)://example.com/Contab/Rapoarte/Rapoarte_obisnuite.asp?strCategorie=ContPart >>>> - NONE/- text/html >>>> >>>> 1259141404.195 0 89.122.203.185 NONE/400 3200 POST >>>> >> (null)://example.com/Contab/NoteContabile/NoteContabUpd.asp?op=MODPOZ&NotaContabId=185 >>>> - NONE /- text/html >>>> >>>> >>>> Squid is: Squid Cache: Version 3.1.0.14-20091120 on Ubuntu Server 9.04 >>>> x86 and the clients are Windows mostly with IE8 but also with older IE, >>>> Opera and Firefox. >>>> >>>> Squid is acting as a reverse proxy in this case and it has worked like >>>> that for at least an year now. Only recently I started seeing these >> kind >>>> of errors. The client receives the usual squid error and a client >>>> refresh solves it in general. >>>> >>> >>> And here bellow is the full error text: >>> >>> ERROR >>> The requested URL could not be retrieved >>> >>> - >>> >> -------------------------------------------------------------------------------- >>> >>> The following error was encountered while trying to retrieve the URL: >>> (null)://example.com/test/ >>> >>> Invalid URL >>> >>> Some aspect of the requested URL is incorrect. >>> >>> Some possible problems are: >>> >>> •Missing or incorrect access protocol (should be “http://”; or similar) >>> >>> •Missing hostname >>> >>> •Illegal double-escape in the URL-Path >>> >>> •Illegal character in hostname; underscores are not allowed. >>> >>> Your cache administrator is email@xxxxxxxxxxxx >>> >> >> Usually spotted when Squid is sent a request for: >> >> GET example.com/somepage HTTP/1.0 >> >> Instead of the correct: >> GET http://example.com/somepage HTTP/1.0 >> >> May also appear for other custom or unknown protocol namespace URIs such >> as: >> GET randomjoes://example.com/somepage HTTP/1.0 >> >> Amos >> >> > > [Once again for the list. Sorry Amos.] > > For further reference this was caused by resolvconf on debian which > triggered a 'squid -k reconfigure' every hour or so (hourly reconnection > of a VPN). > > During the time of the reconfigure (10 secs or so) squid displayed the > above message which, I have to say, is way too misleading. Aha. I have an idea, may take a while to check and fix though. Amos
