Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24312 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51381 invoked by uid 1010); 10 Jul 2006 22:16:37 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 51366 invoked from network); 10 Jul 2006 22:16:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 10 Jul 2006 22:16:37 -0000 X-PHP-List-Original-Sender: pollita@php.net X-Host-Fingerprint: 65.111.164.201 danica.alphaweb.net Linux 2.4/2.6 Received: from ([65.111.164.201:48277] helo=danica.alphaweb.net) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 04/11-16663-3C1D2B44 for ; Mon, 10 Jul 2006 18:16:36 -0400 Received: from talos.alphaweb.net ([69.12.155.129] helo=vait) by danica.alphaweb.net with esmtpsa (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.50) id 1G042m-0005Ko-P8; Mon, 10 Jul 2006 18:15:57 -0400 Message-ID: <000c01c6a46e$7e143850$8f051fac@vait> To: "Andrei Zmievski" Cc: References: <8d4744f0dfe707de33fb151f714bec00@gravitonic.com> Date: Mon, 10 Jul 2006 15:16:19 -0700 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: Re: [PHP-I18N] RFC: Error handling in HTTP input decoding From: pollita@php.net ("Sara Golemon") > Rasmus and I talked about this some more yesterday, and I think there is > an alternate, better approach. > [...snip...] Love it, but we need a few fairly big warnings: "When unicode_semantics is enabled, the $_SERVER['UNICODE_HTTP_INPUT_FAILURE'] variable MUST be checked blah blah blah" put into the manual. Partial decoding of the request body/string should go a long way towards easing the issue for those 20% cases where input decoding will just fail. -Sara P.S. - Has anyone considered offering up an RFC to IETF or W3C about adding a header to the spec? Or just asking the nice Firefox folks to blaze the trail with an X-header? PHP can't be the only web-language dealing with this issue.