>> You're only supposed to change it in your HTML..NOT in the
>> browser's query line..
>
> As well as in header() calls (as already stated in this thread) and in
> javascript calls: document.location.href = 'foo.php?bar=1&var=2' won't
> work either.
Guys, the W3C recommended separator f
Zitat von Jani Taskinen <[EMAIL PROTECTED]>:
> You're only supposed to change it in your HTML..NOT in the
> browser's query line..
As well as in header() calls (as already stated in this thread) and in
javascript calls: document.location.href = 'foo.php?bar=1&var=2' won't
work either.
>
Handling is incorrect for all browsers :-)
if a browser reads a htmlfile (how comes he knows is of no importance, DTD,
guess whatever)
it ALLWAYS knows about & being entity representaion for character '&'
if in any HTML/XML/SGML file a browser reads the character '&' an entity
begins
ther
You're only supposed to change it in your HTML..NOT in the
browser's query line..
--Jani
--
On 22 Jul 2002, Walter A. Boring IV wrote:
>Howdy,
> This may be a tad off topic, but it is related to how php deals with
>building the $_GET superglobal w/ query string vars.
(snip)
on the & subject.. i pressume this is a html only thing, if i try a
header("Location ".$url), where $url has &'s in them php failed to
recognise variables from that..
if the link is made inside an tag in the same way i didnt experience
this problem (using IE5.0 5.5 and 6.0), so i pressum
There is a toggle in your php.ini file you can use to switch this
behaviour of PHP:
arg_separator.output = "&"
-Rasmus
On 22 Jul 2002, Walter A. Boring IV wrote:
> Howdy,
> This may be a tad off topic, but it is related to how php deals with
> building the $_GET superglobal w/ query string v
