Bug 1041626

Summary:	[RFE][python-swiftclient]: Swift Client should use "Expect: 100-continue" header during upload.
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/python-swiftclient/+spec/should-use-100-continue-header
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_new
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:30:08 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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