Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67997 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 70283 invoked from network); 28 Jun 2013 05:12:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jun 2013 05:12:29 -0000 Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.172 as permitted sender) X-PHP-List-Original-Sender: laruence@gmail.com X-Host-Fingerprint: 209.85.217.172 mail-lb0-f172.google.com Received: from [209.85.217.172] ([209.85.217.172:57068] helo=mail-lb0-f172.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 57/0A-34034-B3B1DC15 for ; Fri, 28 Jun 2013 01:12:27 -0400 Received: by mail-lb0-f172.google.com with SMTP id v20so817217lbc.31 for ; Thu, 27 Jun 2013 22:12:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=yEWvrd0rLqNA0+BUi+3jdFmJ0zj4SLUlCT3z7PkuPmM=; b=rkxrhhZ7YwuHrKS4S6BYARUXyF9shBijTstFQmT5TOnZU7RcbmL4T+2y/J+k5pE9Qo 533SDb84tJ4u3C3y44TJeoykVgnpogoE1o1q7lksbSVCbq8qrXq4yzIzfzFt0Vm6Sj+G BTaxAIPC9opl+XLJUdg7PDct0CkWRW+vh5vIjDOvIRi2OOLxxIX/d8b3nTKVnMF8a20g QXaAgj7awOMQg2aqust7bXBMuN0tfPb/bn6M6hDYwgYtk9y7v1PUWvkXjK5Se4QytwHW 6A+k/t2y5a9U9nDTjwYthARD5cNZ9FT9A60NpLuXV5JXNcPqz5SC9sJBoMWJXhaRWi5J PQMA== X-Received: by 10.152.21.99 with SMTP id u3mr5801369lae.18.1372396343748; Thu, 27 Jun 2013 22:12:23 -0700 (PDT) MIME-Version: 1.0 Sender: laruence@gmail.com Received: by 10.114.29.36 with HTTP; Thu, 27 Jun 2013 22:12:03 -0700 (PDT) In-Reply-To: <51CBF60C.9080706@b1-systems.de> References: <51CBF60C.9080706@b1-systems.de> Date: Fri, 28 Jun 2013 13:12:03 +0800 X-Google-Sender-Auth: 9zO9YJPGLpMfL85qlUlnoyfng30 Message-ID: To: Ralf Lang Cc: "internals@lists.php.net" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] I want to work against Bug 44522 - Upload limit 2G From: laruence@php.net (Laruence) Hey: Instead of change the uint to long or size_t, Maybe make the max_file_upload_size 0 means unlimited? like Apached did, ulimited or <=3D 2Gb https://httpd.apache.org/docs/2.2/mod/core.html#limitrequestbody thanks On Thu, Jun 27, 2013 at 4:21 PM, Ralf Lang wrote: > 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. > > > -- > 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 > --=20 Laruence Xinchen Hui http://www.laruence.com/