307s are not followed other than for GET/HEAD, and headers are dropped from those
Bug #1276019 reported by
Andrew Wilkins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Go Windows Azure Client Library |
Fix Released
|
High
|
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:
https:/
https:/
Related branches
lp:~axwalk/gwacl/management-api-307-redirects
- Ian Booth: Approve
-
Diff: 185 lines (+104/-3)3 files modifiedx509dispatcher.go (+35/-1)
x509dispatcher_test.go (+56/-2)
x509session.go (+13/-0)
| Changed in gwacl: | |
| importance: | Undecided → High |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| Changed in gwacl: | |
| status: | Triaged → In Progress |
| Changed in gwacl: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
