You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
What did you do?
When I got a 302 Redirect with Location containing a '\t', the http.client went wrong.
func (c *Client) do(req *Request) (retres *Response, reterr error) {
...
u, err := req.URL.Parse(loc)
if err != nil {
resp.closeBody()
return nil, uerr(fmt.Errorf("failed to parse Location header %q: %v", loc, err))
}
...
}
What did you expect to see?
I'd like to see the Location should replace all '\t' with "" before Parse().
What did you see instead?
The text was updated successfully, but these errors were encountered:
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
When I got a 302 Redirect with Location containing a '\t', the http.client went wrong.
func (c *Client) do(req *Request) (retres *Response, reterr error) {
...
u, err := req.URL.Parse(loc)
if err != nil {
resp.closeBody()
return nil, uerr(fmt.Errorf("failed to parse Location header %q: %v", loc, err))
}
...
}
What did you expect to see?
I'd like to see the Location should replace all '\t' with "" before Parse().
What did you see instead?
The text was updated successfully, but these errors were encountered: