nickva commented on issue #825: Allow urlencoded '+' characters in _scheduler/jobs/<job_id> field URL: https://github.com/apache/couchdb/issues/825#issuecomment-330311639 It would be a different encoding of the same resource. Is encoding the same as representation, I not sure. For example is document `%61` the same as document `a`. > Also, anecdotical, reading around gave me a notion that in web's URL + requires encoding only in query, not in path, but I can't find RFC to back this up. Yap, but mochiweb decodes `+` in path as a space, probably because it reuses the code used for `application/x-www-form-urlencoded`. So if we switched to a different server the code the converting `+` to space would never be called. In other words, this is mostly about bypassing a mochiweb peculiarity. Note in https://tools.ietf.org/html/rfc3986#section-3.3 that the path can contain sub-delims (which include `+`). ``` segment-nz-nc = 1*( unreserved / pct-encoded / sub-delims / "@" ) ; non-zero-length segment without any colon ":" ``` But mochiweb doesn't pass `+` to the application correctly there and decodes it to a space. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
With regards, Apache Git Services
