# header() behaviour (fwd)

- Thread: https://externals.io/message/5059
- Original archive: https://news-web.php.net/php.internals/5059
- Started by Sascha Schumann on 2003-10-29T07:49:34+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #5059 — Sascha Schumann — 2003-10-29T07:49:34+00:00

URL: https://externals.io/message/5059#5059

> 
>
> > […]
>
> 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).

> 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.

> You can
> make PHP understand this by setting the separator in your php.ini file to
> &

    Nope, input separators are always one character wide.

    - Sascha

---

## #5060 — Rasmus Lerdorf — 2003-10-29T08:17:56+00:00

URL: https://externals.io/message/5059#5060 · In reply to: #5059

> > […]
> 
>     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.

> > […]
> 
>     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