On Sat, Jul 19, 2008 at 02:45:26PM +1000, Paul Wratt wrote: > I may be able to "fix" this via some tricky server side code, > pre-header the page as it were, but I need technical details to > get that far. Or is there a way to get more technical data out of > the squid error page or something like that.. The absolute best thing you could do is to perform a packet capture from the client and see exactly what it's sending to squid. You can use ethereal/wireshark or tcpdump for this; at least one must be available for OSX. Possibly the LiveHTTP headers extension for Firefox will be of use too, but a packet capture is always best for showing exactly what the client sent to the proxy. > ======== > ERROR > The requested URL could not be retrieved > > While trying to process the request: > > POST /cgi-bin/swish-query.cgi HTTP/1.0 > Host: www.squid-cache.org > User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; > rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11 > Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 > Accept-Language: en-us,en;q=0.5 > Accept-Encoding: identity,deflate > Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Referer: http://www.squid-cache.org/cgi-bin/swish-query.cgiProxy-Connection: > keep-alive > Cache-Control: max-age=0 > Max-Forwards: 10 > Connection: Keep-Alive I wonder if the above is verbatim, i.e. no copy/paste errors, and if so, if what squid is spitting out is *exactly* what the client sent? There's some obvious problems with headers wrapping to the next line, but that may just be because of how squid displays it and how it was copied.
