Add support for HTTP 100 (continue)

Bug #486742 reported by Duncan McGreggor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
txAWS
New
Wishlist
Unassigned

Bug Description

From Amazon S3 docs:

To configure your application to send the request headers prior to sending the request body, use 100-continue. For PUT operations, this helps you avoid sending the message body if the message is rejected based on the headers (e.g., authentication failure or redirect).

For more information on 100-continue, go to Section 8.2.3 of http://www.ietf.org/rfc/rfc2616.txt.

Changed in txaws:
importance: Undecided → Wishlist
milestone: none → 0.1
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 486742] [NEW] Add support for HTTP 100 (continue)

Note that 100-continue support in the intarwebs is spotty:
 - few HTTP/1.0 proxies don't do the right thing
 - not all 1.1 proxies do either :(

So we should be sure to dead with degraded situations when we do this.

-Rob

Changed in txaws:
milestone: 0.1 → 0.2
Thomas Herve (therve)
Changed in txaws:
milestone: 0.2 → 0.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.