Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:78529 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 30706 invoked from network); 31 Oct 2014 19:04:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 Oct 2014 19:04:20 -0000 Authentication-Results: pb1.pair.com header.from=theanomaly.is@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=theanomaly.is@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.49 as permitted sender) X-PHP-List-Original-Sender: theanomaly.is@gmail.com X-Host-Fingerprint: 74.125.82.49 mail-wg0-f49.google.com Received: from [74.125.82.49] ([74.125.82.49:60344] helo=mail-wg0-f49.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AC/E9-15608-23DD3545 for ; Fri, 31 Oct 2014 14:04:19 -0500 Received: by mail-wg0-f49.google.com with SMTP id x13so7144206wgg.22 for ; Fri, 31 Oct 2014 12:04:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kDLn6t3k7Cm4c8SJ4FNDAG0zwnK+XerJinH3oY4gVYU=; b=AdMDSkUYwO87NnHquAvEzo5+09SDdxqC0xm9szveD23jcB4QVPRc9Pmu2Hwct5Du9A bknFAxrnAmL+454CmpYa+6bn/PvPsBlIE7h43ZvpVymaTLWJ28osLMGweByJTSek3Nfv qdCanrykK9kAvke+0K6tG2rInU1p4B+mMg505rgjsgSwFE+clRtZwQfgcZfrPeIGMuV4 B+cG6dlJol82lgBgG901Bf4TpTAU7Nk3WnF7+aSo1EA4Ul5RDXNKUR696Ju1qlZbY1te BjvoeMvdKYGuKlcjG/jO3Tyk75TX6VbJKZO7rn1kX5zlnKuCXGz2z37g6aFRRQdXQ3xF pPPQ== MIME-Version: 1.0 X-Received: by 10.194.119.193 with SMTP id kw1mr30260073wjb.37.1414782255827; Fri, 31 Oct 2014 12:04:15 -0700 (PDT) Received: by 10.216.123.4 with HTTP; Fri, 31 Oct 2014 12:04:15 -0700 (PDT) In-Reply-To: <5453DC39.8060501@garfieldtech.com> References: <5452B87B.5040009@garfieldtech.com> <0B797CE3-7AFA-4330-9A98-D3CAFC6D6072@ajf.me> <5453B114.6050400@gmail.com> <5453C250.8090803@gmail.com> <5453D6D5.2070705@garfieldtech.com> <5453DC39.8060501@garfieldtech.com> Date: Fri, 31 Oct 2014 15:04:15 -0400 Message-ID: To: Larry Garfield Cc: PHP Internals Content-Type: multipart/alternative; boundary=089e01228626cb1f5a0506bca961 Subject: Re: [PHP-DEV] New Standardized HTTP Interface From: theanomaly.is@gmail.com (Sherif Ramadan) --089e01228626cb1f5a0506bca961 Content-Type: text/plain; charset=UTF-8 On Fri, Oct 31, 2014 at 3:00 PM, Larry Garfield wrote: > On 10/31/14, 1:52 PM, Sherif Ramadan wrote: > >> >> > This RFC has two primary goals in mind: >> >> 1) Expose the parsing/handling of the HTTP request to userland in a >> consistent way >> > > It already is. It's the access TO that parsed data that is currently > clunky. That's a problem worth addressing. No, it's not. There is no way for you to prevent PHP from populating superglobals, or change the way PHP mangles variable names, or change the fact that PHP won't bother populating data in $_FILES or $_GET/$_POST when the request method is PUT or if the content-type is not multipart, for example. None of this is exposed to userland. --089e01228626cb1f5a0506bca961--