Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67923 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 96428 invoked from network); 27 Jun 2013 08:21:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 Jun 2013 08:21:38 -0000 Authentication-Results: pb1.pair.com header.from=lang@b1-systems.de; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=lang@b1-systems.de; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain b1-systems.de designates 84.200.69.220 as permitted sender) X-PHP-List-Original-Sender: lang@b1-systems.de X-Host-Fingerprint: 84.200.69.220 mx1.b1-systems.de Received: from [84.200.69.220] ([84.200.69.220:33084] helo=mx1.b1-systems.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EA/88-51393-016FBC15 for ; Thu, 27 Jun 2013 04:21:36 -0400 Received: from [192.168.1.17] (cable-158-181-84-94.cust.telecolumbus.net [158.181.84.94]) by mx1.b1-systems.de (Postfix) with ESMTPSA id E46DF4075 for ; Thu, 27 Jun 2013 10:17:37 +0200 (CEST) Message-ID: <51CBF60C.9080706@b1-systems.de> Date: Thu, 27 Jun 2013 10:21:32 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: "internals@lists.php.net" X-Enigmail-Version: 1.6a1pre Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2IVLNDWUCTLLJRVLEAXFM" Subject: I want to work against Bug 44522 - Upload limit 2G From: lang@b1-systems.de (Ralf Lang) ------enig2IVLNDWUCTLLJRVLEAXFM Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi, I want to deal with Bug 44522 which disallows uploads > 2G https://bugs.php.net/bug.php?id=3D44522&edit=3D1 Today with PHP cloud solutions, we are running into more situations where this really hurts. Before I begin providing a github patch (as I have no php svn access and I don't think it's needed) against master and possibly 5.5.next: Does anybody know of intricate reasons why the existing patch https://bugs.php.net/patch-display.php?bug_id=3D44522&patch=3Duploads_lar= ger_than_2g_HEAD_v2&revision=3Dlatest could not be included into php 5.5? Or is it only what stas said in 2012: "The patch however needs to be cleaned up (no IGNORE vars, etc.) and changing signature for zend_atoi may not be safe if any code out there presumes it returns int (integer overflow). Also, no reason to use signed long there where we used unsigned long." This would be my first patch against php core. Any pointers apreciated. --=20 Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstra=C3=9Fe 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537 ------enig2IVLNDWUCTLLJRVLEAXFM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlHL9gwACgkQCs1dsHJ/X7Bh7QCglPeY00csBirRWhV4sPLV4HV9 +H4AoM9zzEosZzCltqDfvB7jSlSz7y1u =+0jC -----END PGP SIGNATURE----- ------enig2IVLNDWUCTLLJRVLEAXFM--