Add support for HTTP 100 (continue)
Bug #486742 reported by
Duncan McGreggor
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://
Changed in txaws: | |
importance: | Undecided → Wishlist |
milestone: | none → 0.1 |
Changed in txaws: | |
milestone: | 0.1 → 0.2 |
Changed in txaws: | |
milestone: | 0.2 → 0.3 |
To post a comment you must log in.
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