RE: [PHP-DEV] Re: [PHP-I18N] RFC: Error handling in HTTP input decoding
| From: | Jared Williams | Date: | Mon, 10 Jul 2006 22:54:04 +0000 |
| Subject: | RE: [PHP-DEV] Re: [PHP-I18N] RFC: Error handling in HTTP input decoding | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-24317@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Andrei Zmievski [mailto:andrei@gravitonic.com]
> Sent: 10 July 2006 23:50
> To: Jared.Williams1@ntlworld.com
> Cc: 'Sara Golemon'; internals@lists.php.net
> Subject: Re: [PHP-DEV] Re: [PHP-I18N] RFC: Error handling in
> HTTP input decoding
>
> > W3 standard is to have the charset parameter on the Content-Type
> > header.
> > Unfortunately this breaks too much server side software, so no
> > UserAgents do
> > it.
> >
> > Hence the _charset_ kludge Microsoft introduced awhile back, and
> > Firefox and
> > Opera (afaik) have now adopted.
>
> As far as I know, the form actually has to have a hidden "_charset_"
> input field in order for this to work, no?
Yes, it has to be present. But still I think it could be a useful clue.
Jared