Comment 1:

Assigning to bradfitz because it reminds me of other discussions about URL handling.
Feel free to redirect.

Labels changed: added priority-later, removed priority-triage.

Owner changed to @bradfitz.

Status changed to Accepted.

Comment 2:

Labels changed: added godoc.

Comment 3:

Several possible fixes:
1a) don't navigate to a URL with %2f in it.  (how did that happen?)
1b) if we do get an HTTP request for /foo%2f, redirect to /foo/
2) make the Subdirectories Dirs list link to absolute paths (href="/pkg/net/http/")
instead of relative (href="http").

Owner changed to @griesemer.

Comment 4:

> 1a) don't navigate to a URL with %2f in it.  (how did that happen?)
I've added a bookmark in Firefox with the keyword "pkg" which navigates to
"http://golang.org/pkg/%s".
http://s21.postimg.org/moyc3urmt/keyword.png
A simple example that would trigger this behavior is typing "pkg encoding/" into the
navigation bar which Firefox would translate into "http://golang.org/pkg/encoding%2F".
A more common example would be using different variations of github.com or
code.google.com repositories were you would want to view all packages of a specific user
or all packages contained within a specific repository. (This is when running godoc
locally of cause).
While it is possible to teach yourself not to add a trailing "/" at the end of such
requests, I do think this should be resolved in godoc and not at the client.

Comment 5:

Labels changed: added go1.2.

Comment 6:

Owner changed to ---.

Comment 7:

Andrew, do you have a preference between 1b) and 2) above?

Comment 8:

I think it's too late to be making changes to godoc. Let's leave this as is for Go 1.2.
If the same shortcut goes to pkg/encoding%2Fbinary we aren't going to redirect to
encoding/binary. These URLs are invalid. Let's leave it there.

Labels changed: removed go1.2.

Comment 9:

Labels changed: added go1.3maybe.

Comment 10:

Labels changed: added release-none, removed go1.3maybe.

Comment 11:

Labels changed: added repo-tools.

Close the issue for now as it has remained inactive for more than 6 months.

Anyone with more insight into the current status may re-open the issue or add a comment about the current progress.