On Wed, 29 Oct 2003, Sascha Schumann wrote: > > Actually, & is the way you need to write it if you are going to be > > perfectly standards-compliant. > > That is correct for URLs in HTML. It is incorrect for HTTP headers > (there is no entity decoding involved).
True, I should read instead of skim these messages. > > It's just that nobody does this. > > Really? My applications supply their own php.ini and always > contain > > arg_separator.output = "&" > > which is also listed in php.ini-dist. Ok, so very few people do this. -R -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
