Joop Beris wrote:
On Thursday 05 March 2009 10:27:44 you wrote:
You mean it sends only:
"POST http://example.com/blah\n"; ??
No, sorry! I misread the wireshark capture. The exact post request is as
follows:
POST /cms/index.php HTTP/1.1
Host: www.nederweert.nl
User-Agent: jupload/0.87
Referer: http://www.nederweert.nl/cms/
From: info@xxxxxxxxxxx
Accept: text/*;q=1.0, */*;q=0.0
Cache-Control: no-cache
Pragma: no-cache
Accept-Charset: ISO-8859-1;q=0.9,*;q=0.1
Connection: close
Cookie: PHPSESSID=d69c9e49d7de14f4738ed65e6cf1e4b0
Content-Type: multipart/form-data; boundary=--JUPLOAD--
BOUNDARY--4zo0gHIyRX--JUPLOAD-BOUNDARY--
Content-Length: 158064
This causes Squid to respond with an "invalid request" response.
Hmm, okay.
If "BOUNDARY" actually starts on a new line in the trace that will be
the error.
If it was emailer wrap, squid is broke. (This is where I say try a newer
one so we can accurately track down if it still needs a fix and what.)
You may want to make the ACL sightly more restrictive:
http_access allow Java POST
instead of just a global POST permitted.
Thank you, that's a good idea! Will do that.
Thanks,
Joop
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE13
Current Beta Squid 3.1.0.6
