On Fri, Jan 01, 2010 at 12:36:12AM +1300, Amos Jeffries wrote: > > I've taken a good look at the trace files on this. It's clear that the > client is in fact not sending the whole initial POST. > > What I see happening is that the server early response gets relayed by > Squid and if the connection is not aborted Squid receives a small > further portion of data from the client before it abruptly stops and > starts sending the re-send POST with auth details. > > Since the client has indicated a certain length X of data then only > sends N bytes the start of second request is lost and the server > complains that some random bytes mid-way down the repeat POST are an > invalid request method "verb". > Ah, ok. I missed that :) > To get this going we are going to have to add to the patch a bit to make > Squid delay the relayed reply until the initial POST is fully received. > Do you need help with this? I don't know the squid code but should be able to muddle through if you can give a pointer. > PS: This has pushed Squid very, very close to the wanted behavior for > Expect-100 HTTP/1.1 requests/replies. Thanks guys. > Thanks for looking in to this. -- Brett Lymn "Warning: The information contained in this email and any attached files is confidential to BAE Systems Australia. If you are not the intended recipient, any use, disclosure or copying of this email or any attachments is expressly prohibited. If you have received this email in error, please notify us immediately. VIRUS: Every care has been taken to ensure this email and its attachments are virus free, however, any loss or damage incurred in using this email is not the sender's responsibility. It is your responsibility to ensure virus checks are completed before installing any data sent in this email to your computer."
