Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upnet/http: 307 and 308 status codes should not change method on redirect #16840
Comments
subbu05
changed the title
quentinmit
changed the title
This comment has been minimized.
This comment has been minimized.
|
/cc @bradfitz |
gopherbot
pushed a commit
that referenced
this issue
Sep 26, 2016
Updates #13994 Updates #16840 Change-Id: Ia3cad5c211e0c688a945ed6b6277c2552592774c Reviewed-on: https://go-review.googlesource.com/29760 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This comment has been minimized.
This comment has been minimized.
|
Dup of #10767 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have gone through few golang issues on HTTP redirect.
I have referred to HTTP RFC https://tools.ietf.org/html/rfc7238 and conveys that client need not change the PUT/POST method when 307 or 308 response is seen in the request.
Note: This status code is similar to 301 (Moved Permanently)
([RFC7231], Section 6.4.2), except that it does not allow changing
the request method from POST to GET.
But with golang 1.7 I see that net http client is using HTTP GET when 307 or 308 response is seen. This violates the http rfc which says HTTP method will not be changed for 307 or 308 http response.