> Geoff Howard wrote: > > I would regard the behavior below to be incorrect - so the million > > dollar question is what is the correct behavior: > > > > Can GET parameters be separated by & instead of > > & according to the W3C, etc? > > I don't think so. & is the delimiter, not &. What is when amp; is > really needed? & is only the escaped & in XML and HTML. So if you > write an <a href=""/> there must be & in theory, but it's parsed as > &. If you use & in href, it's only the "intelligence" of the browser to > not interpret it as starting of an entity. But in the URL itself, it > must be &, not & >
Sorry for being an idiot. & is valid in the html as delimeter, but the browser should take it out so that <a href="http://localhost:8080/cocoon/samples/system/request.html?foo=bar&f ee=fi">test</a> sends you to: http://localhost:8080/cocoon/samples/system/request.html?foo=bar&fee=fi with the unescaped ampersand. The reason I was confused was because I remembered a problem I encountered in the past with & as the delimeter in html being passed through, but I believe the problem there was more complicated - javascript was passing the & literally IIRC. Mea Culpa, Geoff --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
