Using Terminal-0.2.5.7svn-23159, When i open an url containing commas from terminal, the right part of the url is stripped.. Example : http://www.lemonde.fr/web/article/0,1-0@2-651865,36-830373@51-830376,0.html Opened url : http://www.lemonde.fr/web/article/0,1-0@2-651865,36-830373@51-830376 Is this a Terminal problem, or an invalid url (but handler by web browsers) ?
The URL is invalid. The comma must be escaped.
For my information, do you have a RFC for this assertion, or which RFC do you follow to recognise an URL ? If i refer to http://www.ietf.org/rfc/rfc1738.txt, a comma is not invalid in an URL : Thus, only alphanumerics, the special characters "$-_.+!*'(),", and reserved characters used for their reserved purposes may be used unencoded within a URL. If i refer to http://www.ietf.org/rfc/rfc3986.txt (newer), it is valid to use a comma to separate parts of an url : Thus, characters in the reserved set are protected from normalization and are therefore safe to be used by scheme-specific and producer-specific algorithms for delimiting data subcomponents within a URI. And finally, why Terminal handles the others commas, and not the last ? If i encode/escape the last comma as '%2c', the part of url at the right of the last comma encoded as ',' is still stripped.. I really don't want to make this a real _issue_, i just want to understand how it works, and what rfc do you follow..
Low priority, minor severity, but still a bug imho... :)
Depends on bug #2454, esp. since firefox/seamonkey cannot handle non-escaped commata.
Nah, this IS bug #2454. Neither Terminal nor exo-open strip off the part after the comma, but Firefox does it. Firefox expects the comma to be escaped. *** This bug has been marked as a duplicate of bug 2454 ***