This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 748 - & in URLs not parsed correctly with GET requests
Summary: & in URLs not parsed correctly with GET requests
Alias: None
Product: Validator
Classification: Unclassified
Component: check (show other bugs)
Version: 0.7.1
Hardware: All All
: P2 trivial
Target Milestone: ---
Assignee: Terje Bless
QA Contact: qa-dev tracking
Depends on:
Reported: 2004-05-27 14:16 UTC by Radoslav Atanasov
Modified: 2006-10-31 01:41 UTC (History)
0 users

See Also:


Description Radoslav Atanasov 2004-05-27 14:16:49 UTC
If I want to check my website via the

URL, the URL which is actually parsed is
page=2. I tried using & instead of & in the URL and the problem still 
persists. If I submit the URL with the form on the site (which uses POST), 
there are no problems.

It is not a big of a problem, but you might be interested.
Comment 1 David Dorward 2004-05-27 14:27:46 UTC
& has special meaning in URIs, as it does in HTML. However, they should be url
encoded, not converted to HTML entities.

The correct representation of & in a URI (when not being used as a field
seperator in a query string) is %26.

Browsers convert this automatically when a form is submitted.
Comment 2 Tim Rutter 2006-01-13 10:49:35 UTC
This is still a problem. e.g.
While validating a page and you type:-
Into the "Address:" input. It goes to:-
This does not work and it should.

You have to type:-
Into the "address:" input. Which goes to.

When on the front page to the validator and you type in a URL to check it first
HTML encodes the URL and then URLencodes it.

URLs should only be URL encoded. so what is in the "Address:" input is the same
as what you would enter into a browsers Address bar and not what would be in the
html source.
Comment 3 Olivier Thereaux 2006-10-31 01:41:52 UTC
No idea why this has been reopened (nor do I, honestly, understand comment #2).