307 redirect not handled

Bug #1195445 reported by Gavin Panella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Go Windows Azure Client Library
Fix Released
High
Unassigned

Bug Description

When running example/management/run:

{{{
...
Deleting VM disk...
panic: DELETE request failed (307: Temporary Redirect)

goroutine 1 [running]:
main.checkError(0xf8401973c0, 0xf840193860)
        .../example/management/run.go:43 +0x4e main.ExerciseHostedServicesAPI(0xf840069c20, 0x0)
        .../example/management/run.go:177 +0x1f9e
main.main()
        .../gwacl/example/management/run.go:82 +0x1a7

goroutine 2 [syscall]:
created by runtime.main
        /build/buildd/golang-1.0.2/src/pkg/runtime/proc.c:221

goroutine 3 [syscall]:
created by addtimer
        /build/buildd/golang-1.0.2/src/pkg/runtime/ztime_amd64.c:72
}}}

I would expect the request to be retried at the new location specified in the response, with the same request method. From Wikipedia:

307 Temporary Redirect (since HTTP/1.1)
In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For instance, a POST request should be repeated using another POST request.

Gavin Panella (allenap)
description: updated
Raphaël Badin (rvb)
Changed in gwacl:
status: Triaged → Fix Committed
Changed in gwacl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.