Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:121248 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 33536 invoked from network); 6 Oct 2023 13:44:20 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 6 Oct 2023 13:44:20 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 750731804C1 for ; Fri, 6 Oct 2023 06:44:19 -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-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 6 Oct 2023 06:44:18 -0700 (PDT) Received: by mail-pg1-f174.google.com with SMTP id 41be03b00d2f7-578a62c088cso2567394a12.1 for ; Fri, 06 Oct 2023 06:44:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1696599858; x=1697204658; darn=lists.php.net; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=wIayQamisBaKny65Z2ivThRH8NGr/iJX4ZaNtBt4t/M=; b=fc5lyy335xwOYzEjXdic3P73RbD/sFqZW3An59Vpsv3cebj4KLQQHGS+liX3PKKIhz cWsWYeWzt6fsKGP/5QvM1uSVhSY5xRCeJaW7tuEqAfM21TkLisGI1Rwa3LOxN8UZcrP5 FaBUzo8l3qjAmMOajpcgiMv1RWjud+PaaQFfc5iCvFd/nuNzhkDrmruWeV+K63d1C8f0 PgzG3PPY3PrtA2C3FQGBFUs4niI1Wf2QrOqGuwUV9mTU/Um4R7pf16EH1WoR3SXZJu08 OS8J/hFtyMjdyic8QFClf8XemDHlTBNTiCsMQ2kNXPwS+IKLN/eGSd/CGPctZx+jW2dF LbkQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696599858; x=1697204658; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=wIayQamisBaKny65Z2ivThRH8NGr/iJX4ZaNtBt4t/M=; b=spneYXuB//yzvOEfwsen2i2e0epohpuOh+/W2dxu757lMoIPBsQZ0ENFIM5ReYrEUt SA9u7ZeITEoXY8K/83jmivf2zSEZa41nZ0ZRrLkpeD/K3p3BTnNNgMHzQR/V2Iv/edYN DIh5U1Z08wkZfd9aQtHVFcty2tjM3RGJBCyTvIC+Jv3CxYQSGJMEq7DXZLaRsTmqKpQl AF2IruB5rwIuQntcu9pSIFjiY3xOUWolCN38NPUUc4xvC7Wp3jSh+GyG1/KSpNe71xxg o5p+3FYxt8P5K2oWs5kaYcQILwdDDllOecGntMeFkbhOdocFzojpaxz9l08+BvmW+a5s 5MIQ== X-Gm-Message-State: AOJu0Yz4cGmhKipoFR2+UWp3g6jKHL8Z0x5zPmfE+JcCUj7tSSON/f6k 9vYL2FmHie5SJHl2RebZMH+ZMrgLbsBEqwr/rbrIWrWjY5kiag== X-Google-Smtp-Source: AGHT+IEoL+AT35l7vuJAvqG8pHFzvXI3mXl7uEjWKYDL2mffpAP4BCWBUE/mENMNT/n4/D6YIkQL82OQKIrl6F4Y0fI= X-Received: by 2002:a17:90a:3ea3:b0:277:3569:29fb with SMTP id k32-20020a17090a3ea300b00277356929fbmr8567152pjc.11.1696599857542; Fri, 06 Oct 2023 06:44:17 -0700 (PDT) MIME-Version: 1.0 Date: Fri, 6 Oct 2023 15:44:06 +0200 Message-ID: To: PHP internals Content-Type: text/plain; charset="UTF-8" Subject: [RFC][Under discussion] RFC1867 for non-POST HTTP verbs From: tovilo.ilija@gmail.com (Ilija Tovilo) Hi everyone A while ago I wrote an e-mail about RFC1867 (multipart/form-data) not being parsed by PHP for non-POST requests. https://externals.io/message/120641 I'd like to announce an RFC that proposes adding a new function called parse_post_data() to expose the existing functionality to userland, so that the mechanism can be used for other HTTP verbs. https://wiki.php.net/rfc/rfc1867-non-post As opposed to the semantics I suggested in the previous thread, this proposal returns the parsed result instead of populating it directly to the superglobals, and it accepts an optional input stream. Let me know if you have any feedback. Ilija