Re: [RFC][Vote] RFC1867 for non-POST HTTP verbs

From: Date: Tue, 23 Jan 2024 19:41:04 +0000
Subject: Re: [RFC][Vote] RFC1867 for non-POST HTTP verbs
References: 1  Groups: php.internals 
Request: Send a blank email to internals+get-122236@lists.php.net to get a copy of this message
On Mon, Jan 22, 2024 at 1:24 AM Ilija Tovilo <tovilo.ilija@gmail.com> wrote: > I started the vote on the "RFC1867 for non-POST HTTP verbs" RFC. > https://wiki.php.net/rfc/rfc1867-non-post > > Apologies for not seeing the discussion period, but I'll qualify my "No" vote, because I'm actually +1 on the general concept, and this is just a little bikeshedding (this RFC will pass even with a no vote from me). 1/ This function reaches into the SAPI to pull out the "special" body data. That's great, but what about uses where providing an input string makes sense. For that, and for point 2, I'd suggest http_parse_query(string $query, ?array $options = null): array|object. 2/ request_ represents a new psuedo-namespace, functions are easier to find and associate if we keep them grouped. I recommend 'http_` because it compliments the very related function http_build_query(), and for the version of this function which refers directly to the request: http_parse_request(?array $options = null) : array|object. -Sara

« previous php.internals (#122236) next »