Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:120693 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 40121 invoked from network); 27 Jun 2023 09:01:26 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 27 Jun 2023 09:01:26 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 67C991804D0 for ; Tue, 27 Jun 2023 02:01:25 -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=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ot1-f48.google.com (mail-ot1-f48.google.com [209.85.210.48]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Tue, 27 Jun 2023 02:01:24 -0700 (PDT) Received: by mail-ot1-f48.google.com with SMTP id 46e09a7af769-6b7474b0501so1954024a34.1 for ; Tue, 27 Jun 2023 02:01:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687856484; x=1690448484; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=yDCU87E6kX4Naxfh+ilSGxJq6VPuftrCeM7XorCmO8w=; b=ktrIqwnQdfNfpT5M3Q02euVLR5i4LqlHS8Foeep463VRgL64joV9ZZIQJAcW4LFwU+ g7rv1CUj2g1KEc+qhnkCX0Qjvus4KtRje+sl4EW3o0kaH8EWsHzRZT4zQrnEQMaGHvkl 1W3rgExkGVFbqT5Gd+1aSZxt2w6qDhH5RHD/dnFXGESh0mWjcRgkW3FArfkGvPIJ/vrt l/Kbk1pX40MJ3893SzQW22vIfghuBLOnUR8Waft2SZhKlTumX1ZavItI//YU3Dd8qbk3 vZIUTn/hXERUxlubWiDyQgp8tn8YR34gNfUIVzckfM2VLiHABYvcjo4jN49P8X13adFL zCGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687856484; x=1690448484; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=yDCU87E6kX4Naxfh+ilSGxJq6VPuftrCeM7XorCmO8w=; b=ElOOmS5OIYoz3sN+tGPVf9jIgsIeyirFYax7xWHtD4Sv2R2MOrmFyk1QuIw4fR0QZY qZ8SccaAktOZ6bLc2jxatx0E7/4A91yojqvndJ4rEe0IkiMz1Bz3eMjJ7Hgg9yXap/8x UAPYy/6aoCtnztMdANn8wckAdrVI6LsGwUOgIn1xwJMHRT5R6ffIsJCr+v7E4N6mVnmZ DojEetYGXFI0CzRyIkRF94XE0lEldmKFhZkXTH8EY4fKp+veT2P+eVdu3cJmSiiSxsgR T7eC8SPtbg0mI2VxPvYPNln6eZFrgUeS8zfERVpvvJ18Cv32uXXe0xqeJ9CqeOtgqvS5 n2qw== X-Gm-Message-State: AC+VfDxKSPtrk4dV27BDx5pv5hUDk+4YmMwwqQ7jql0eoWAlOeBWuxw3 8q2X7QS/EEhE7WdrRX+u6cm7Eas7yqbeS+tUee6AmDcXyxA= X-Google-Smtp-Source: ACHHUZ5Y8uYfo9ZdHRxf/tW2opVgqSScIMyjQQXgqHrrXTFK26SmMS08+poJkS7e9wzvfN/JXd+KTErGoKfGncaaB/A= X-Received: by 2002:a05:6870:76a6:b0:1a9:d5c9:4e5d with SMTP id dx38-20020a05687076a600b001a9d5c94e5dmr25934824oab.30.1687856483827; Tue, 27 Jun 2023 02:01:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Tue, 27 Jun 2023 11:01:12 +0200 Message-ID: To: PHP internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] RFC1867 (multipart/form-data) PUT requests From: tovilo.ilija@gmail.com (Ilija Tovilo) Hi Ben, Hi Rowan On Mon, Jun 26, 2023 at 8:55=E2=80=AFPM Ben Ramsey wrot= e: > > > On Jun 20, 2023, at 06:06, Rowan Tommins wrot= e: > > > > On Tue, 20 Jun 2023 at 10:25, Ilija Tovilo wro= te: > > > >> Introduce a new function (currently named populate_post_data()) to > >> read the input stream and populate the $_POST and $_FILES > >> superglobals. > > > > How about "request_form_populate_globals"? The word "form" seems a bit out of place (even though it appears in both multipart/form-data and application/x-www-form-urlencoded), because this function is mainly targeted at PUT/PATCH requests for REST APIs. Maybe request_body_populate_globals? > Another option for the name: `populate_multipart_form_data()`. I avoided the term "multipart" because the function technically also works for application/x-www-form-urlencoded requests. It's less necessary for the reasons outlined in my previous email, but it would allow for consistent handling of such requests for all HTTP methods. Some people on GitHub voiced that they would prefer an INI setting. Therefore I will create an RFC accordingly. Ilija