Opening a /user/ page fails for usernames with a space (" ") in them

[avarab@…]

Usernames that have spaces in them e.g. "Ævar Arnfjörð Bjarmason" will be opened as ​http://www.openstreetmap.org/user/%C3%86var.

This bug was introduced in r2034 (see ticket:3379).

To reproduce try opening ​the dump of Iceland and doing a wildcard search.

[Gubaer]

(In [2042]) fixed #3382: Opening a /user/ page fails for usernames with a space (" ") in them

[avarab@…]

Replying to Gubaer:

(In [2042]) fixed #3382: Opening a /user/ page fails for usernames with a space (" ") in them

This is still broken. If I click on my username JOSM sends me to ​Ævar+Arnfjörð+Bjarmason instead of the correct ​Ævar Arnfjörð Bjarmason. I.e. it escapes " " as "+" instead of "%20".

[Gubaer]

Not sure whether this is a defect on JOSMs side. Isn't it perfectly "legal" to encode a blank with either %20 or + according to the ​RFC ?

Anyway, in case of OSM web site we probably better switch to %20-encoding.

[Mormegil]

Replying to Gubaer:

Not sure whether this is a defect on JOSMs side. Isn't it perfectly "legal" to encode a blank with either %20 or + according to the ​RFC ?

No, a space in the path component of a HTTP URI must be encoded as %20. See ​RFC 3986, section 3.3, the “+” character is a normally valid character in that part of a URI (as a member of sub-delims), and does not encode any other character. Some web servers/software might use + as an encoding for space (and escape “+” characters, if they can appear in the specific context, using percent encoding), but that is entirely their local choice, not a universal standard.

[Gubaer]

(In [2073]) fixed #3382: Opening a /user/ page fails for usernames with a space (" ") in them