Comment 1:

Some discussion on the topic has happened on golang-dev:
https://groups.google.com/d/topic/golang-dev/j7VmXb9nd5M/discussion

Owner changed to ---.

Comment 2:

We can regrettably "fix" the Client redirect back to returning two non-nil values, but
it'll have to be documented/tested.
I'm less sure about RoundTrip.  It's always been documented on the interface about what
the expectations are for implementations of a RoundTripper.  What's the issue there?
I'll accept this bug for now, but patches welcome.  I won't start working on it until
Monday at least, and I'll change the status to "Started" here when I do start.

Owner changed to @bradfitz.

Comment 3:

RoundTrip didn't catch me, and I don't personally mind as much. It's still a stable API
being changed, though.
Thanks for looking at this, Brad.

Comment 4:

Now that I re-look at the docs (the same as shipped with Go 1), I care about RoundTrip
even less.  Note:
http://golang.org/pkg/net/http/#RoundTripper
    // [...] RoundTrip should not
    // attempt to interpret the response.  In particular,
    // RoundTrip must return err == nil if it obtained a response,
    // regardless of the response's HTTP status code.  A non-nil
    // err should be reserved for failure to obtain a response.
... there's even a "must" in there.

Comment 5:

Gustavo, the original change does say:
"Revision: f7839a55036e 
Author:   Brad Fitzpatrick <bradfitz@golang.org> 
Date:     Tue Jun 19 09:10:14 2012 
Log:      net/http: clarify client return values in docs 
Also, fixes one violation found during testing where both 
response and error could be non-nil when a CheckRedirect test 
failed.  This is arguably a minor API (behavior, not 
signature) change, but it wasn't documented either way and was 
inconsistent & non-Go like.  Any code depending on the old 
behavior was wrong anyway."

Comment 6:

Regarding that commit message: maybe I was wrong to declare all such code wrong, but I
couldn't think of a case where it would be useful to stop a redirect but care about
getting the response as you stopped it.

Comment 7:

Brad, any news on this?

Comment 8:

Easy fix. I just haven't done it yet. It would be a good project for today, though,
since I have limited Internet access.

Labels changed: added priority-soon, go1.1, removed priority-asap.

Comment 9:

http://golang.org/cl/6429044

Comment 10:

This issue was closed by revision dfd7f18.

Status changed to Fixed.