On 06/04/2011 22:38, Tory M Blue wrote:
<SNIP>
how about trying to dump the http headers to see what is going on there?
deubg setions 11 23 55
is this a forward or reverse proxy?
can it be that some server is sending a 300 status code to squid but
without URL?
Eliezer
Nope clean install on 2.7STABLE9 and the first hour or so no error
messages but now I'm getting them
2011/04/06 12:33:46| storeClientReadHeader: no URL!
2011/04/06 12:34:02| storeClientReadHeader: no URL!
2011/04/06 12:34:12| storeClientReadHeader: no URL!
2011/04/06 12:34:12| storeClientReadHeader: no URL!
2011/04/06 12:34:33| storeClientReadHeader: no URL!
2011/04/06 12:34:34| storeClientReadHeader: no URL!
2011/04/06 12:34:35| storeClientReadHeader: no URL!
2011/04/06 12:34:37| storeClientReadHeader: no URL!
2011/04/06 12:35:03| storeClientReadHeader: no URL!
2011/04/06 12:35:03| storeClientReadHeader: no URL!
2011/04/06 12:35:40| storeClientReadHeader: no URL!
2011/04/06 12:35:50| storeClientReadHeader: no URL!
2011/04/06 12:35:52| storeClientReadHeader: no URL!
2011/04/06 12:36:17| storeClientReadHeader: no URL!
2011/04/06 12:36:18| storeClientReadHeader: no URL!
2011/04/06 12:36:18| storeClientReadHeader: no URL!
Since this was a absolutely fresh install, clean cache directory, this
is either a request coming in or something. We did make some changes
with headers, but since this was a clean install, can't believe it's
the apache changes from the app servers.
Very strange, would like to identify
Tory
