Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69308
Return-Path: <tjerk.meesters@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 68401 invoked from network); 24 Sep 2013 06:05:16 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 24 Sep 2013 06:05:16 -0000
Authentication-Results: pb1.pair.com header.from=tjerk.meesters@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=tjerk.meesters@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.51 as permitted sender)
X-PHP-List-Original-Sender: tjerk.meesters@gmail.com
X-Host-Fingerprint: 209.85.128.51 mail-qe0-f51.google.com  
Received: from [209.85.128.51] ([209.85.128.51:33594] helo=mail-qe0-f51.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id D8/10-02182-A9B21425 for <internals@lists.php.net>; Tue, 24 Sep 2013 02:05:15 -0400
Received: by mail-qe0-f51.google.com with SMTP id ne12so2879424qeb.10
        for <internals@lists.php.net>; Mon, 23 Sep 2013 23:05:12 -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=HqvUkGZ/sd1hVMXLlmoZYKRfyVwHtwnUZesmY6s6P9A=;
        b=gmlY2rVjCYbPUr5BMW/xfSuS7hxIN1UueZXgJZB3iC/AaLcvn129EH/UZuJ5fCjMXj
         bJdB8OjOCKuDR1wMdgppcQ+1YZvMbM3qZaO+4hTrD8kUtHqcnu8PoNe9WQbLBOhH8g7w
         AC2nV9bQO4/0Mnx6Q3FBOyDgFQ2V6YWKZF78nvAS5MxovxwxmatRoK37GBTyrsHOiTW5
         7gGeUdhQl7LEbASgVZKGnCNq0fj3/jBObzP9ZpixaIxek0xBb+VwGHNu9ilrK8t5HzL6
         hFZuOsMS4eiA3kMnVnVwy04Cm8EthBSw4z1jcKFLB9lJWvZQkdSLIPqZyQLqOYxeOILt
         boCg==
MIME-Version: 1.0
X-Received: by 10.224.54.129 with SMTP id q1mr27056780qag.19.1380002712099;
 Mon, 23 Sep 2013 23:05:12 -0700 (PDT)
Received: by 10.49.61.227 with HTTP; Mon, 23 Sep 2013 23:05:12 -0700 (PDT)
In-Reply-To: <CAHsEcH9WOXf2E7C0=GZqmLLMck2h-nzEgQzO0mCbT3m80AW9+g@mail.gmail.com>
References: <CAHsEcH9WOXf2E7C0=GZqmLLMck2h-nzEgQzO0mCbT3m80AW9+g@mail.gmail.com>
Date: Tue, 24 Sep 2013 14:05:12 +0800
Message-ID: <CAHMUw2Fs2ag50B0KTHCzYKCNSff7kXqHNsFivRdjsZqyVggx7A@mail.gmail.com>
To: Dave <catch.dave@gmail.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a11c3127e71a12904e71aeb73
Subject: Re: [PHP-DEV] Parsing PUT data
From: tjerk.meesters@gmail.com (Tjerk Meesters)

--001a11c3127e71a12904e71aeb73
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Sep 24, 2013 at 1:19 PM, Dave <catch.dave@gmail.com> wrote:

> Hi All,
>
> Firstly, let me know if this is particularly spammy/inappropriate for this
> list.
>
> I just wanted to get some feedback on a long-time feature request (2011)
> about treating PUT the same as POST in terms of re-using the existing form
> parser. See https://bugs.php.net/bug.php?id=55815 for details.
>
> Normally, I wouldn't have posted this to internals, but as you can see,
> there's been no movement on this for a long time.
>
> In short, in order to provide a proper REST service that supports multipart
> form data, we need someway to parse data sent via PUT (data is available
> via php://input, but it needs to be parsed).
> Could be as simple as adding $_PUT / $_FILES for PUT data.
>

Perhaps it might be a better idea to expose the multipart parser as a
function, so that you can bind the decoded body to either an object or
array. The trick is to keep `is_uploaded_file()`, etc. working, though.


>
>
> What's the best way to move this forward?
> Do I need to create a patch/RFC? Or is this something someone can just pick
> up?
>
>
> Thanks,
> Dave
>



-- 
--
Tjerk

--001a11c3127e71a12904e71aeb73--