Well, I see this:
15.562 http readv of 2c779c251220f8afce08bcec69277e32.rix offsets => 2 collapsed 2
...
21.370 http readv of 7c2a6579c7a01088577744c8b461dae4.pack offsets => 8 collapsed 3
Which means that we successfully issued several multi-part requests.
It would seem that Savannah isn't always broken in sending multiple Content-Type headers. I wonder if there is a transparent proxy somewhere that is breaking this.
On bug #198646 Henrik Nordström comments that Savannah is indeed wrong in giving 2 Content-Type headers.
Robert- How would you suggest diagnosing this? Change our urllib wrappers to recognize 2 Content-Type headers and abort with a message to the user? Do some sort of search to see:
if found_boundary.startswith('--') and found_boundary[2:].rstrip() in expected_boundary
Which would be a likely indication that we miss-parsed the expected_boundary string.
Well, I see this: fce08bcec69277e 32.rix offsets => 2 collapsed 2 8577744c8b461da e4.pack offsets => 8 collapsed 3
15.562 http readv of 2c779c251220f8a
...
21.370 http readv of 7c2a6579c7a0108
Which means that we successfully issued several multi-part requests.
It would seem that Savannah isn't always broken in sending multiple Content-Type headers. I wonder if there is a transparent proxy somewhere that is breaking this.
On bug #198646 Henrik Nordström comments that Savannah is indeed wrong in giving 2 Content-Type headers.
Robert- How would you suggest diagnosing this? Change our urllib wrappers to recognize 2 Content-Type headers and abort with a message to the user? Do some sort of search to see:
if found_boundary. startswith( '--') and found_boundary[ 2:].rstrip( ) in expected_boundary
Which would be a likely indication that we miss-parsed the expected_boundary string.