Thus said Joel Bruick on Tue, 27 May 2014 21:55:06 -0400: > It's really an HTML form thing [1] that only applies to the query > portion of the URL. In the path component, we technically should be > percent-encoding spaces and leaving any instances of "+" alone, which > would then allow you to reference such files normally.
Does the specification for URIs apply in this case? http://tools.ietf.org/html/rfc3986 If I read the RFC correctly, it seems that 0x2b (+) is allowed in a URI as a sub-delim character unless it conflicts: sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "=" Section 2.2: ... If data for a URI component would conflict with a reserved character's purpose as a delimiter, then the conflicting data must be percent-encoded before the URI is formed. ... The purpose of reserved characters is to provide a set of delimiting characters that are distinguishable from other data within a URI. URIs that differ in the replacement of a reserved character with its corresponding percent-encoded octet are not equivalent. Not sure if this helps ore muddies the implementation. :-) Andy -- TAI64 timestamp: 40000000538555eb _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
