Re: Transparent SessionIDs

There are a bunch of FAQs linked to from the W3C validator. To be strictly compliant, you cannot use & in a link... it should be &amp;, which the browser interprets as &. FWIW, I've been sticking to & not &amp;, but the validator is correct in listing it as a non-compliant problem. Justin on 18/10/02 10:04 AM, Owen Prime (owen@noggin.com.au) wrote: > Has anyone come across this before? > > Have been using transparent session ids for donkeys but when recently > running a page through the W3C validator I noticed something. The source of > the page had a line like: > > <a > href="content.php?id=5&PHPSESSIONID=16738gd8172d8787c8s7df">label</a> > > My code was obviously just <a href="content.php?id=5">label</a> and PHP > added the rest. > > My question is this: To keep doc type compliant, should the "&" that PHP > adds for the transparent session id be htmlentitised to be "&amp;" > producing the line: > > <a > href="content.php?id=5&amp;PHPSESSIONID=16738gd8172d8787c8s7df">label</a> > > Does PHP strive for a particular doc type? The function nl2br() has been > XHTML compliant since 4.0.5. > > I was going to post it as a bug, but would like a second opinion first. > > Cheers, > > Owen Prime > http://www.noggin.com.au