Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107354 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 76226 invoked from network); 1 Oct 2019 10:19:49 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 1 Oct 2019 10:19:49 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id BF5902CD115 for ; Tue, 1 Oct 2019 01:00:24 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Tue, 1 Oct 2019 01:00:24 -0700 (PDT) Received: by mail-io1-xd2e.google.com with SMTP id h144so45477654iof.7 for ; Tue, 01 Oct 2019 01:00:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=XeYPznRnKUhVrGHaUouQ5s7z7tDuiMLA4QV5JpSW7+A=; b=QQjRr7w3dNKelD3HD9771z9SxDCZllE+SAVAeK7v4KgSciAdQjLDFZRmXTrEJg67W3 0zy+58sCH6vgYFH8KGqjMl4GexsMNN6DoLfUjf7TjXNR8KAbYJmBjuKXcfLU78NrYUT7 pRBSth1I1/BE/kXTL9PQBjUEQIrrMkuHXsynKFGE2ufuC8RN9znUNzema7bzxsb1m4PE kgNw3N0otmfhFryZwO1rsjGAn2Zxytv2gRb8gy8vV9jNOeMEEyC9oQ+gXABGJx56gH0+ 8eOz7o1OBc8Xj02zmDUSn6dQNnC1+hQ6NusHywh7UVyAvF/CwdvZht99p0eZKSfA+7HK FwIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=XeYPznRnKUhVrGHaUouQ5s7z7tDuiMLA4QV5JpSW7+A=; b=JR55vHpm9oFPWeATQDqUrUzUCXVQwsPXCzUmbLxGD4g1p6A6TVVSneXeJWOhso12Hs l51KmozC6FlgqsBAa2H85Z6pOVCyixKrTx+qL/Juq64+UcIdC7Bxpf/VFDzrE1jjYDhF 23mMvUmx1uC6ecrqACqXLBn3EXA9t7MGargMFAr8sCdBehUufuTk/1ikGjXHEkgdRGe/ qz4cWc9w+0F46sCuJppwLqalTsZEEH5iUXqNTf///tHFA5Y4PxMXT4uRzSRF+XgJ8+hf Ku76G3F5GjNNkxZv8RTbzOWuvdyiP1xtEPSqIuzw9mI+/m+r3Ae1hVcUwyDLlWB7WdXl h+uw== X-Gm-Message-State: APjAAAVBrHP6ZIOWhA1kLPORfL/0uy6IJEkvSmpdP0XmHCjQ82S8tDLo dKeGu4Op9nOi1kXuHpM8GyROXpTgWRVif8QDVqAqrLDY+9k= X-Google-Smtp-Source: APXvYqyOht9gOq+2nmb2ufvSOoO8PJR5rmzvLvViJCBwU5JrwCSu+1B1tnwnUmivdsEmddoyRE54kR6PeX6SMfwmicY= X-Received: by 2002:a92:1e09:: with SMTP id e9mr5275489ile.176.1569916823144; Tue, 01 Oct 2019 01:00:23 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 1 Oct 2019 10:00:11 +0200 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary="00000000000092113e0593d4bed8" X-Envelope-From: Subject: Error when POST / upload limits are exceeded From: benjamin.morel@gmail.com (Benjamin Morel) --00000000000092113e0593d4bed8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi internals, One thing that always bugged me is how PHP silently ignores data that exceeds the limits defined in php.ini. For example, posting a form exceeding post_max_size results in empty $_POST and $_FILES, with no error message whatsoever. This has bugged a few more people than just myself, if I believe this StackOverflow question with 37k views. Another example is max_file_uploads: if I upload more files that the configured value, the subsequent files are silently ignored, and only the first n files appear in $_FILES. I'd like to work on an RFC to make all these errors in PHP 8 (ideally with a way to catch the error, but I'm not sure how to do that), but would love to get some feedback/ideas before venturing in an RFC. Thank you. =E2=80=94 Benjamin --00000000000092113e0593d4bed8--