Bug 1041626 - [RFE][python-swiftclient]: Swift Client should use "Expect: 100-continue" header during upload.
Summary: [RFE][python-swiftclient]: Swift Client should use "Expect: 100-continue" hea...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/pyth...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 18:19 UTC by RHOS Integration
Modified: 2015-03-19 17:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:30:08 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description RHOS Integration 2013-12-12 18:19:48 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/python-swiftclient/+spec/should-use-100-continue-header.

Description:

During upload, if the Auth token is expired, the swift client
unnecessarily uploads the chunks and fails at the end.
Instead, we could have a fail fast mechanism using the
100-continue handshake. Only if the client receives a 100 continue
from swift, it should continue uploading the chunks.
Otherwise, if a 401 is received, it should fetch a fresh auth
token and retry the request.

Specification URL (additional information):

None
Note You need to log in before you can comment on or make changes to this bug.