net/url: better path resolving

[moraes]

The resolvePath function used by URL.ResolveReference doesn't cover all cases described
in the RFC 3986, and specially it fails to resolve some of the normal and abnormal
examples from sections 5.4.1 and 5.4.2 [1].

The code repository tip succeeds in some of these tests, but several still fail:
http://play.golang.org/p/F0ApSaXniv

[1] http://tools.ietf.org/html/rfc3986#section-5.4.1

[moraes]

Comment 1:

I created a codereview with a simplified resolvePath function and tests for the RFC
cases: https://golang.org/cl/7203059

[moraes]

Comment 2:

This same patch also fixes this: http://play.golang.org/p/089b-_xoNe

[rsc]

Comment 3:

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

Status changed to Accepted.

[rsc]

Comment 4:

This issue was closed by revision 82e3ca7.

Status changed to Fixed.