Re: [aether-dev] Strange handling of + in version portion of GAV

[Stephen Connolly <stephen.alan.connolly@xxxxxxxxx>]

Hmmm perhaps you are correct... and only query string encoding maps space to +...

F*cking URI spec and it's "handy" helping

On 29 July 2013 11:58, Stephen Connolly <stephen.alan.connolly@xxxxxxxxx> wrote:

+ is the alternative encoding of the space character, e.g.

/foo%20bar/ and /foo+bar/ are equivalent

but

<version>foo+bar</version> should be mapped to /foo%2bbar/ and not /foo+bar/ which if subjected to URI decode/encode roundtrip can end up as /foo%20bar/

On 29 July 2013 11:34, Benjamin Bentmann <bentmann@xxxxxxxxxxxx> wrote:

Stephen Connolly wrote:

http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/build-monitor-plugin/1.0+build.14/

Has anyone noticed that we don't seem to be encoding the + character when
mapping GAV to URL?

AFAIK, "+" doesn't need encoding when used within a URI's path segment, cf. section 3.3 of RFC 2396.


Benjamin
_______________________________________________
aether-dev mailing list
aether-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aether-dev