Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121405 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 90948 invoked from network); 18 Oct 2023 16:07:17 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Oct 2023 16:07:17 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 247D11804D0 for ; Wed, 18 Oct 2023 09:07:17 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_NEUTRAL,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS30827 82.113.144.0/20 X-Spam-Virus: No X-Envelope-From: Received: from xdebug.org (xdebug.org [82.113.146.227]) by php-smtp4.php.net (Postfix) with ESMTP for ; Wed, 18 Oct 2023 09:07:16 -0700 (PDT) Received: from localhost (localhost [IPv6:::1]) by xdebug.org (Postfix) with ESMTPS id 2D43610C066; Wed, 18 Oct 2023 17:07:15 +0100 (BST) Date: Wed, 18 Oct 2023 17:07:15 +0100 (BST) To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= cc: Ilija Tovilo , PHP internals In-Reply-To: <6fccfe47-21ac-fa5b-e52e-28064f26125b@bastelstu.be> Message-ID: <91b89c73-03f8-31df-cfab-84009b3d3bce@php.net> References: <6fccfe47-21ac-fa5b-e52e-28064f26125b@bastelstu.be> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-2116892626-1697645235=:32886" Subject: Re: [PHP-DEV] [RFC][Under discussion] RFC1867 for non-POST HTTP verbs From: derick@php.net (Derick Rethans) --8323329-2116892626-1697645235=:32886 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE On Fri, 6 Oct 2023, Tim D=C3=BCsterhus wrote: > On 10/6/23 15:44, Ilija Tovilo wrote: > > https://wiki.php.net/rfc/rfc1867-non-post > >=20 >=20 > Regarding the cleanup of the files, perhaps the files could be read into = a > `php://temp` stream > (https://www.php.net/manual/en/wrappers.php.php#wrappers.php.memory)? I don't think that reading potentially large files into memory is a=20 great idea. It is precisely because of the memory issue that PHP's=20 existing POST handler writes files to disk, instead of leaving their=20 content available through an entry in $_FILES. cheers, Derick --8323329-2116892626-1697645235=:32886--