Edit report at https://bugs.php.net/bug.php?id=55815&edit=1
ID: 55815
Comment by: dawidgora at icloud dot com
Reported by: catch dot dave at gmail dot com
Summary: PUT request data should be parsed just like POST
Status: Suspended
Type: Feature/Change Request
Package: Streams related
Operating System: All
PHP Version: 5.4.0beta1
Block user comment: N
Private report: N
New Comment:
Any update on this one? 2011 was 12 year ago lol
Previous Comments:
------------------------------------------------------------------------
[2023-05-15 14:04:30] lucas at decrock dot me
As I was developing a REST API, I came across an issue that surprised me: the API doesn't
support PATCH requests. It's disappointing to see such a basic feature missing in 2023, and it
could potentially reflect poorly on the professionalism of the API's developers.
------------------------------------------------------------------------
[2023-01-05 10:07:19] cyril dot garsaud at gmail dot com
PHP 8.2 has been released, with no fixes for this critical issue. Developers are forced to find
workarounds and move away from REST guidelines because of this bug. Eventually, they might abandon
the PHP language...
------------------------------------------------------------------------
[2022-02-05 18:38:44] svaneekelen at avt dot nl
It is unbelievable that this is still not implemented after 11 years. This is one of the main
reasons why people leave php and consider it a old language. I think I don't need to repeat
what the other members on this form said but this is ridiculous there is no reason to not implement
a fix for this on the php side. The least that can be done is to upload in this case the file to
$_FILES what doesn't even happen in php 7.4 with put request. While it seems that the php dev
team does not even want to burn their fingers on this massive bug for 2 days because that is what it
would take because the logic exists already elsewhere. The least that php should do is bring in a
stable solution to read these files because this is basic functionality.
------------------------------------------------------------------------
[2020-06-25 13:55:31] me at daz dot one
I've been trying to figure out how to work with this issue without having to break RESTful
convention and boy howdie, what a rabbit hole, let me tell you.
I'm adding this anywhere I can find in the hope that it will help somebody out in the future.
I've just lost a day of development firstly figuring out that this was an issue, then figuring
out where the issue lay.
After trawling through a good few RFCs for php core, the core development team seem somewhat
resistant to implementing anything to do with modernising the handling of HTTP requests. The issue
was first reported in 2011, it doesn't look any closer to having a native solution.
That said, I managed to find a PECL extension called apfd (always populate form data). I'm not
really very familiar with pecl, and couldn't seem to get it working using pear. but I'm
using CentOS and Remi PHP which has a yum package.
I ran:
yum install php-pecl-apfd
and it literally fixed the issue straight away (well I had to restart my docker containers but that
was a given).
I believe there are other packages in various flavours of linux and I'm sure anybody with more
knowledge of pear/pecl/general php extensions could get it running on windows or mac with no issue.
If you're looking for a clean fix for this issue, I'd personally advise taking a look.
------------------------------------------------------------------------
[2020-06-24 14:29:41] me at daz dot one
I know this has been said MANY times but I can't believe this is still not implemented.
I get that it may not have been so essential in 2011 but in 2020 we now live in an age of REST APIs.
Having to break RESTful convention due to this feature not being implemented is literally crazy.
Is there anything I (or anybody else that needs this) can do to speed up getting it implemented?
Thanks.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=55815
--
Edit this bug report at https://bugs.php.net/bug.php?id=55815&edit=1