Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118577 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 46965 invoked from network); 7 Sep 2022 21:46:57 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 7 Sep 2022 21:46:57 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 76B2E180384 for ; Wed, 7 Sep 2022 14:46:57 -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.2 required=5.0 tests=BAYES_40,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-qv1-f52.google.com (mail-qv1-f52.google.com [209.85.219.52]) (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 14:46:54 -0700 (PDT) Received: by mail-qv1-f52.google.com with SMTP id y9so8788555qvo.4 for ; Wed, 07 Sep 2022 14:46:53 -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=ONFgOtSt8wAaw0Y6NcUScesWLsWpwGOX8rleAfupbts=; b=nl23VEAdycKJHm2bEFFCqhj3ES1JBA/G775ErzlM67cVha/qKgPWTPW2Qq0Hf15RsK HP+V+tk2LwgH/gBK7n1Z2ovgEeAq3aJNpHxkugaEaZ6vCN6LT9R3vSapvwYUhaF3QyJb yYxXMbSlZW2ykCZEUuzXwyEW9kq8ZyESfHB+zRraR5Krro7UI6+QsMBSvpzL1RWcLMYx EHKQLCMuE4iS00/9n1yPpeliG6fQr3SpXfe8Ixe+iniBz7ilcxiN+PVDBzvRRKXvxAek x6g1DVEixtr1ZWFuzF/lmyoA1iFec1pDbw28koa4bU28plQ4XjCGaQbH6WFbGNYyWlV4 4xIQ== 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=ONFgOtSt8wAaw0Y6NcUScesWLsWpwGOX8rleAfupbts=; b=Z6iDFUyWp5GO5zQjar3oyeSQtf5/H9YnCiptqEPQZ+nV5b/Wo+oDj1SWwlugRWhqsC dfj6eQvy/r+7S5Kr1sgTV3ojD8Oyc5mwmTXit4AcQs1KixBbQMV2CiatrQfVaGIOrZ78 tj5pd6wnfLX8NSE0qcjHjaRE5Qa3NvimHbiPxsiSfDgooGLJvyPn/DecceiLz6kC02VC zHmYIhXy2olxN9LvMP6epskw0tX073tiPMjA/LWPRITW/e28j9p2cImlDClIw56tQu3b P65eQXG0H4xxZjezQVhZAqe9cey8EPD1XNkz86H+rlBI6+6xFCY+lrMelXQLuRq+CG92 mlyw== X-Gm-Message-State: ACgBeo0+UefdhpBhsOnOKpYljZVee4Uv83CkEhzgP0Pbu3ky7ApVUCQh WhB2+Sj/+ThggP121NVuas7JWXQrEEKJD7CydRY= X-Google-Smtp-Source: AA6agR40gI51dafkyUntWmX7XG/wMTu7gkHx38xKlYc8NKZ2CY9ZKMBYVzRI6Dgd3+Gz81enCMSosDeBjVj2XFv6V5E= X-Received: by 2002:a05:6214:2a83:b0:4aa:b1a6:9536 with SMTP id jr3-20020a0562142a8300b004aab1a69536mr4992090qvb.39.1662587213354; Wed, 07 Sep 2022 14:46:53 -0700 (PDT) MIME-Version: 1.0 References: <6318b012.250a0220.e968b.9528SMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: Date: Wed, 7 Sep 2022 14:46:48 -0700 Message-ID: To: juan carlos morales Cc: Ben Ramsey , PHP Internals List Content-Type: multipart/alternative; boundary="00000000000042997505e81d403c" Subject: Re: [PHP-DEV] Re: Increase maximum size of an uploaded file to 50Mbyte From: kris.craig@gmail.com (Kris Craig) --00000000000042997505e81d403c Content-Type: text/plain; charset="UTF-8" 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? > > But for sure such a change should be well marked in case is merge. > > I did not take look at the PR as that can wait also. > > Lets respect the RFC protocol and wait the specified time to see if someone > else comes with something. > > By the Way... This needs an RFC right? > Yes, most definitely. --00000000000042997505e81d403c--