note 62736 deleted from function.http-build-query by hholzgra
| From: | hholzgra@php.net | Date: | Thu, 02 Aug 2012 13:36:26 +0000 |
| Subject: | note 62736 deleted from function.http-build-query by hholzgra | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-189771@lists.php.net to get a copy of this message | ||
Note Submitter: Colin Guthrie
----
@ xangelusx
You said that "It is actually illegal to set arg_separator.output to & ("and amp
;") as every character is considered a seperator according to the documentation."
I don't think this is correct. arg_separator.input maybe, but not the output. How can PHP
encode my URLs (that is what this setting is used for, e.g. on URL rewriting etc.) with more than
one separator? It doesn't make sence for that variable.
I have personally used & as a separate for output for years in order to create valid XHTML
output via PHP.
I long ago wrote a function to do this for me, but depending on where I use the output, I sometimes
want & and sometimes just a plain old & (think putting the value in a href=""
versus using it in a Location: header). Unfortunatly, I can see no way to deprecate my function just
yet, as this built in function is lacking that distinction (an optional argument would be perfect
IMO)