Re: PHP 4.0 Bug #8274 Updated: PHP not w3c compliant
| From: | Stanislav Malyshev | Date: | Sun, 17 Dec 2000 17:22:45 +0000 |
| Subject: | Re: PHP 4.0 Bug #8274 Updated: PHP not w3c compliant | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-41667@lists.php.net to get a copy of this message | ||
AM>> Someone informed us on the dev@horde.org list that '&' is in
AM>> fact not a valid URL character.
AM>>
AM>> http://www.w3.org/TR/html4/appendix/notes.html (section
AM>> B.2.2)
AM>> for more information. Basically, some browsers attempt to
AM>> interpret whatever follows it as an SGML entity, and much
AM>> confusion results. It should either be '&' or ';'
Well, that's funny that W3C decides on it some 20 years after it should,
but I fear since most webservers still have & as their argument separators
in CGI, it's good to stick to that still.
What other people here think on that?
--
Stanislav Malyshev, Zend Products Engineer
stas@zend.com http://www.zend.com/ +972-3-6139665 ext.115