Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118580 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 57893 invoked from network); 8 Sep 2022 00:27:37 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 8 Sep 2022 00:27:37 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 608AE180546 for ; Wed, 7 Sep 2022 17:27:36 -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=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,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-il1-f170.google.com (mail-il1-f170.google.com [209.85.166.170]) (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 ; Wed, 7 Sep 2022 17:27:35 -0700 (PDT) Received: by mail-il1-f170.google.com with SMTP id r7so8429693ile.11 for ; Wed, 07 Sep 2022 17:27:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=dgkN3tx5igMwAvfa+WxZ3EPeRBg0Omy+r+bPZuNDNI4=; b=AkEDM2dbHLucdbrE39xHP8ThvfHh+eD7l0nDI14sn7khxDDHfa8sg4IIytVov6iUJP aa8JHcjhDSJCkmh9S/178Lwh8cf5khvUF2ln24b0dsuaeT7wGCIjx8+LtHtrMVQym4sX YW+XeqkDHBlBRDkOU4Of833PT/sfXeorC+09Qd14YTuDWrDNawMx9G+IyE2E+Ys7ZJGn Pu2ZUVykilz0/j3AE17kYuKtQGI34l3lhvuVYMH4xonoqImu/91+oH+c4F9BJ0hRIRG6 qw4DdHqfdXOw++yYxrCOkq5SCeZDnlLyQjc0DDVZQeJTmAq5czZnJh3aVeT0mxCfHXLR /1yQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=dgkN3tx5igMwAvfa+WxZ3EPeRBg0Omy+r+bPZuNDNI4=; b=y4G7Lt4Zms0MOKlxS1iEdlOKFPzGc2U1JrbfQke9JgvlSFP9Wpc5gxcnnw+H0oRXUl HwVmdqQBvC7p4Hg3FhiC6vK/g5pQW9Mhuu1LYKYgZM1rbz9m9w6PGJEj5f87+fsl7u3M 5kHk1mWfrkhwUHlVK/VsFn8WZpqEam3cKHSMqXLK3FG8y5aEc/Fv85k0Uvq/MyxBb0We tjIqyMJz5TfH+3Cg5Szjf3Qg9l84kvDe7aOm5dCIzdnwerHspX2UsKCgQAKyp3OzEhQu lCw5mRPGzgJvG3o2rkq/4RFeNKWx/NWhfnadBVmmX6hw9ETcyZjXoxvTDLC4ygf/JPop zcyQ== X-Gm-Message-State: ACgBeo0cVTBIkCTvOqnviylH14g8zpUi4WmhvRIKLamqhTToZQB8e+KE HiXS+JKF//5iC8fYY89SppiscnbiKYQvuUTsSfc= X-Google-Smtp-Source: AA6agR7qPsbG5BzMIDDQbAAqYyiZGyQt6R0zVydiv313+kawOb5w3eIjv/cZjXmc1Qt+UzGK1R5esOyCeLdoarpG5Lw= X-Received: by 2002:a05:6e02:1cae:b0:2f1:d173:1558 with SMTP id x14-20020a056e021cae00b002f1d1731558mr581349ill.234.1662596855392; Wed, 07 Sep 2022 17:27:35 -0700 (PDT) MIME-Version: 1.0 References: <6318b012.250a0220.e968b.9528SMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Date: Thu, 8 Sep 2022 01:27:24 +0100 Message-ID: To: Kris Craig Cc: juan carlos morales , Ben Ramsey , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000f8760605e81f7ee1" Subject: Re: [PHP-DEV] Re: Increase maximum size of an uploaded file to 50Mbyte From: davidgebler@gmail.com (David Gebler) --000000000000f8760605e81f7ee1 Content-Type: text/plain; charset="UTF-8" On Wed, Sep 7, 2022 at 10:47 PM Kris Craig wrote: > On Wed, Sep 7, 2022 at 11:38 AM juan carlos morales < > dev.juan.morales@gmail.com> wrote: > > > I looked for a potential problem out of doing such a change but I could > not > > find anything. > > > > Then I'd say it's a no-brainer. The current 2 MB limit is simply outdated > and needs to be increased to something a little more realistic. > > That said, I think 50 MB may be pushing it. How about 20 MB, instead? > > That's the obvious question; why 50MB? Why not 10, 20 or [fill in the blank]MB? I have no objection in principle to increasing the shipped default but whatever number is picked, most devops/sysadmins are going to change it to suit their needs. I would classify this as an unnecessary but harmless change, since you should be tuning your engine configuration in any public facing deployment anyway. --000000000000f8760605e81f7ee1--