Re: Please make possible to read Unicode Web addresses
I stand correct on the percentage-encoding not being Unicode. Well IMO this shouldn't even be a problem, is kinda of common this percentage-encoding and all browsers should recognize it and make the proper translation. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
Security Issue? why? the characters are put in a form of hexadecimal representation preceded by a percentage symbol, is not mystery or it doesn't do anything than that; is just represented on another way for some reason, maybe hiding the URI/L or some new standard, but is not security-related in any way I can think of. It's kinda of common so it should be a standard supported by most browsers by now IMO. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
On 2/21/12 4:20 PM, gjikkl wrote: I stand correct on the percentage-encoding not being Unicode. Well IMO this shouldn't even be a problem, is kinda of common this percentage-encoding and all browsers should recognize it and make the proper translation. Browsers do recognize percent-encoding when found in a domain, path, file, query (following a ), or fragment (following a #). But percent-encoding is not allowed for separation characters or protocols. In your URI http%3A%2F%2Fi283.photobucket.com%2Falbums%2Fkk284%2Fdismadrosa13%2Fline.gif: http is the protocol. You have %3A%2F%2F in place of ://, which are separation characters where percent-encoding is illegal. Not only does SeaMonkey not support the use of percent-encoding for separation characters, but Internet Explorer (the only other browser installed on my PC) also does not support it. i283.photobucket.com is the domain. You have %2F in place of / four more times, which are more separation characters (1) between the domain and the path, (2) two times within the path (albums/kk284/dismadrosa13), and (3) between the path and the file (line.gif). I previously referred to RFC 3986. Please read it. Note that is a special character in HTML. Since RFC 3986 specifies its use as the separation character before a query in a URI, HTML provides for amp; in place of in a URI. Browsers translate amp; into when ever it is found, in a URI or in plain text content. I do not think browsers support %26 for that purpose within a URI. -- David E. Ross http://www.rossde.com/. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
gjikkl wrote: I stand correct on the percentage-encoding not being Unicode. Well IMO this shouldn't even be a problem, is kinda of common this percentage-encoding and all browsers should recognize it and make the proper translation. Did you bother reading the RFC 3986 at ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt which David Ross provided (particularly sections 2.2 and 2.4) and his explanation. If you had you would have seen that your opinion doesn't really matter because the RFC explicitly states that URIs that differ in the replacement of a reserved character with its corresponding percent-encoded octet are not equivalent. and therefore; no standards compliant browser should translate the uri you provided as you suggest. ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
On 2/21/12 5:28 PM, David E. Ross wrote: On 2/21/12 4:20 PM, gjikkl wrote: I stand correct on the percentage-encoding not being Unicode. Well IMO this shouldn't even be a problem, is kinda of common this percentage-encoding and all browsers should recognize it and make the proper translation. Browsers do recognize percent-encoding when found in a domain, path, file, query (following a ), or fragment (following a #). But percent-encoding is not allowed for separation characters or protocols. In your URI http%3A%2F%2Fi283.photobucket.com%2Falbums%2Fkk284%2Fdismadrosa13%2Fline.gif: http is the protocol. You have %3A%2F%2F in place of ://, which are separation characters where percent-encoding is illegal. Not only does SeaMonkey not support the use of percent-encoding for separation characters, but Internet Explorer (the only other browser installed on my PC) also does not support it. i283.photobucket.com is the domain. You have %2F in place of / four more times, which are more separation characters (1) between the domain and the path, (2) two times within the path (albums/kk284/dismadrosa13), and (3) between the path and the file (line.gif). I previously referred to RFC 3986. Please read it. Note that is a special character in HTML. Since RFC 3986 specifies its use as the separation character before a query in a URI, HTML provides for amp; in place of in a URI. Browsers translate amp; into when ever it is found, in a URI or in plain text content. I do not think browsers support %26 for that purpose within a URI. By the way, the software that handles URIs is in the Gecko core. This means that SeaMonkey, Firefox, Thunderbird, and other Gecko-based applications all refuse to support percent-encoded separation characters. -- David E. Ross http://www.rossde.com/. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
Interviewed by CNN on 21/02/2012 22:24, gjikkl told the world: Security Issue? why? the characters are put in a form of hexadecimal representation preceded by a percentage symbol, is not mystery or it doesn't do anything than that; is just represented on another way for some reason, maybe hiding the URI/L or some new standard, but is not security-related in any way I can think of. I didn't SAY it's a security issue, but I suspect it could be. Basically, this would offer more ways to obfuscate URLs. I know no legitimate reason to obfuscate URLs -- but I do know that this is a basic technique for scammers. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my Cray Y-MP. * Added by TagZilla 0.7a1 running on Seamonkey 2.7.2 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
Interviewed by CNN on 19/02/2012 17:07, Rufus told the world: ...as an aside, why does SM often change the ' and some other characters contained in the website name information in a Bookmark to what appear to be Unicode characters? Most annoying. I don't remember noticing this behavior. Could you please give an example of a website so affected? -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my IBM PCjr. * Added by TagZilla 0.7a1 running on Seamonkey 2.7.2 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
David E. Ross wrote: I previously referred to RFC 3986. Please read it. Note that is a special character in HTML. Since RFC 3986 specifies its use as the separation character before a query in a URI, HTML provides foramp; in place of in a URI. Browsers translateamp; into when ever it is found, in a URI or in plain text content. I do not think browsers support %26 for that purpose within a URI. Actually, it's not hard to find places on the web where a link passes a URL to a script that does something before redirecting, so you get something like this: a href=http://www.originaldomain.com/cgi-bin/a2/out.cgi?u=http://targetdomain.com/specificpage.html;display text/a In such a context, it's not unusual for the embedded URL to be percent-encoded for benefit of the script that will read it. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
On 2/21/12 10:10 PM, Paul B. Gallagher wrote: David E. Ross wrote: I previously referred to RFC 3986. Please read it. Note that is a special character in HTML. Since RFC 3986 specifies its use as the separation character before a query in a URI, HTML provides foramp; in place of in a URI. Browsers translateamp; into when ever it is found, in a URI or in plain text content. I do not think browsers support %26 for that purpose within a URI. Actually, it's not hard to find places on the web where a link passes a URL to a script that does something before redirecting, so you get something like this: a href=http://www.originaldomain.com/cgi-bin/a2/out.cgi?u=http://targetdomain.com/specificpage.html;display text/a In such a context, it's not unusual for the embedded URL to be percent-encoded for benefit of the script that will read it. In that case: 1. A browser is not handling percent-encoded separation characters; a script is handling them. 2. The script must convert the percent-encoded separation characters back into the actual separation characters before sending the URI to a Web server. -- David E. Ross http://www.rossde.com/. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
Interviewed by CNN on 19/02/2012 14:52, gjikkl told the world: I'd like SeaMonkey be able to read http%3A%2F%2Fi283.photobucket.com%2Falbums%2Fkk284%2Fdismadrosa13%2Fline.gif as http://i283.photobucket.com/albums/kk284/dismadrosa13/line.gif I didn't study the subject, but: 1. I expect that there are good security reasons for *not* doing that, and 2. I expect that this would go against the relevant web standards. -- MCBastos This message has been protected with the 2ROT13 algorithm. Unauthorized use will be prosecuted under the DMCA. -=-=- ... Sent from my Etch-a-Sketch. * Added by TagZilla 0.7a1 running on Seamonkey 2.7.2 * Get it at http://xsidebar.mozdev.org/modifiedmailnews.html#tagzilla ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
MCBastos wrote: Interviewed by CNN on 19/02/2012 14:52, gjikkl told the world: I'd like SeaMonkey be able to read http%3A%2F%2Fi283.photobucket.com%2Falbums%2Fkk284%2Fdismadrosa13%2Fline.gif as http://i283.photobucket.com/albums/kk284/dismadrosa13/line.gif I didn't study the subject, but: 1. I expect that there are good security reasons for *not* doing that, and 2. I expect that this would go against the relevant web standards. ...as an aside, why does SM often change the ' and some other characters contained in the website name information in a Bookmark to what appear to be Unicode characters? Most annoying. -- - Rufus ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
On 2/19/12 8:52 AM, gjikkl wrote: I'd like SeaMonkey be able to read http%3A%2F%2Fi283.photobucket.com%2Falbums%2Fkk284%2Fdismadrosa13%2Fline.gif as http://i283.photobucket.com/albums/kk284/dismadrosa13/line.gif Thanks. That URI also does not work with Internet Explorer. Both work when non-ASCII characters are percent-encoded in the domain name, path, file, query, and fragment but not as URI delimiters. Your URI has percent-encoding for the :// delimiters that are supposed to follow the http, which is not allowed. By the way, percent-encoding is not Unicode. See RFC 3986 at ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt. (You might have to copy and paste the RFC's URI into your browser because of bug #575376.) -- David E. Ross http://www.rossde.com/. Anyone who thinks government owns a monopoly on inefficient, obstructive bureaucracy has obviously never worked for a large corporation. © 1997 by David E. Ross ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
Re: Please make possible to read Unicode Web addresses
David E. Ross wrote: On 2/19/12 8:52 AM, gjikkl wrote: I'd like SeaMonkey be able to read http%3A%2F%2Fi283.photobucket.com%2Falbums%2Fkk284%2Fdismadrosa13%2Fline.gif as http://i283.photobucket.com/albums/kk284/dismadrosa13/line.gif Thanks. That URI also does not work with Internet Explorer. Both work when non-ASCII characters are percent-encoded in the domain name, path, file, query, and fragment but not as URI delimiters. Your URI has percent-encoding for the :// delimiters that are supposed to follow the http, which is not allowed. Not so simple. On my IE 9, I couldn't get the flashing line until I replaced all percent encodings with the corresponding ASCII characters. I got a total rejection when the URI delimiter was percent-encoded, but as I worked my way down the chain, Photobucket kept telling me the image had been deleted until I finally replaced the last one, when it suddenly discovered it. On the other hand, Wikipedia pages do generally work as long as the URI delimiter and domain name are not percent-encoded. So perhaps some servers are smarter than others. -- War doesn't determine who's right, just who's left. -- Paul B. Gallagher ___ support-seamonkey mailing list support-seamonkey@lists.mozilla.org https://lists.mozilla.org/listinfo/support-seamonkey
