[dev] Fwd: [bugs] [Bug 533] Changed - broken urls in generated code

[Anil Madhavapeddy]

Quoting Max Kalika <max@the-triumvirate.net>:

> Quoting Chuck Hagenbuch <chuck@horde.org>:
> 
> > I've seen this issue mentioned a few times, but no one seems to be
> > terribly good about it - for one thing, does he even have the 
> > right take on things, and for another, do we want to push to fix 
> > this in 2.3?
> 
> I did notice, when working on my own things, that there was a problem of
> query strings with &-delimited fields would get interpreted erroneously.
> I think I tried it on every version of every popular browser and only 
> IE4 has this problem.  


I don't understand this - as I understand it, SGML entities consist
of three portions: the ERO (entity reference open) which is an 
ampersand by default, the entity name itself, and a reference
end.

The reference end should only consist of an REFC (the reference close
delimiter), which is a semicolon by default, a character which is
invalid in an entity name, or a reference function code (not appliacable
to HTML afaik)

So for HTML, the only really valid entity form is '&blah;'.  How can
a browser interpret a substring of a URL as an entity without the
semicolon in there (urlencoded, of course) ?

-- 
Anil Madhavapeddy, <anil@recoil.org>