307s are not followed other than for GET/HEAD, and headers are dropped from those

Bug #1276019 reported by Andrew Wilkins on 2014-02-04
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Go Windows Azure Client Library
Andrew Wilkins

Bug Description

When gwacl moved away from curl, correct handling of 307s (as far as Azure is concerned) regressed. Followed redirects drop all the headers of the original request (including x-ms-version), and only GET/HEAD are followed as per the HTTP spec, but it seems Azure wants us to follow them for POST and DELETE too.

See also:

Related branches

Andrew Wilkins (axwalk) on 2014-02-04
Changed in gwacl:
importance: Undecided → High
assignee: nobody → Andrew Wilkins (axwalk)
Andrew Wilkins (axwalk) on 2014-02-04
Changed in gwacl:
status: Triaged → In Progress
Andrew Wilkins (axwalk) on 2014-02-05
Changed in gwacl:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers