Re: Transparent SessionIDs

I understand why it is putting it in the URL, my question was really to do with the encoding of the & symbol. I am pretty sure it needs to be entitised. Take for example a textbox: <input type="text" value="&quot;"> This is the only way to get a double-quote inside the text box. So by reverse logic, if you wanted to literally put the text "&quot;" in there you would have to use "&amp;quot;". The same applies with all tag arguments including the href argument in the <a> tag. Cheers, Owen Prime http://www.noggin.com.au Jonathan Sharp wrote: > I believe taht & is correct. As far as the PHPSESSIONID showing up, if > php isn't able to set a cookie, then it passes it in the urls. > > -js > > > Owen Prime 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 >>