Closed Bug 261644 Opened 22 years ago Closed 22 years ago

Not handling of encoded ampersands(&) in url

Categories

(Core :: DOM: HTML Parser, defect)

x86
Linux
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: dviano, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5 The ampersand should be encoded as an html entity _always_ in web pages. Mozilla handle all of them well, except when opening an URL with an encoded ampersand. See http://www.htmlhelp.com/tools/validator/problems.html#amp for more information. Not encoded ampersands in URLs show you the intended page. As example: http://wiki.lug.fi.uba.ar/tiki-view_blog_post.php?blogId=5&postId=141 <--- Bad encoded http://wiki.lug.fi.uba.ar/tiki-view_blog_post.php?blogId=5&amp;postId=141 <--- Right encoded Reproducible: Always Steps to Reproduce:
er, can you attach an HTML page to this bug showing the problem? (https://bugzilla.mozilla.org/attachment.cgi?bugid=261644&action=enter) this is supposed to work...
(In reply to comment #1) > er, can you attach an HTML page to this bug showing the problem? > (https://bugzilla.mozilla.org/attachment.cgi?bugid=261644&action=enter) > > this is supposed to work... Douh!. My mistake. I'm really sorry, this was bogus. My mistake even though I really check it many times. Now I've seen this was another mistake in component which encoded the ampersands twice. Sorry once again. p.d.: Although http://wiki.lug.fi.uba.ar/tiki-view_blog_post.php?blogId=5&amp;postId=141 pasted in the URL entry from the navigation toolbar doesn't work. I'll for now close this bug. Feel free to reasign this if you consider that it should work.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
thanks for checking, marking verified :) &amp; in the url bar should not be decoded - it is only the html parser which should decode &amp;.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.