Closed
Bug 324055
Opened 19 years ago
Closed 19 years ago
Size limit on xpi upload too small
Categories
(mozilla.org Graveyard :: Server Operations, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: carey, Assigned: aravind)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051217 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051217 Firefox/1.5
My extension is about 9MB and fails to upload with the following error. More about the extension in particular can be found at
http://www.cmiss.org/cmgui/mozcmgui
Request Entity Too Large
The requested resource
/developers/additem.php
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
Apache/2.0.46 (Red Hat) Server at addons.mozilla.org Port 80
Reproducible: Always
Steps to Reproduce:
1. login
2. browse to select xpi file to upload
3. click next to begin upload
Actual Results:
Request Entity Too Large
The requested resource
/developers/additem.php
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
Apache/2.0.46 (Red Hat) Server at addons.mozilla.org Port 80
Expected Results:
Successful upload of xpi file
My extension is platform specific so I need to upload an xpi for each platform too. ie my account needs to be capable of having 50MB per release...
Updated•19 years ago
|
Assignee: Bugzilla-alanjstrBugs → morgamic
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 324566 has been marked as a duplicate of this bug. ***
Comment 2•19 years ago
|
||
The max filesize limit is being hit because it's probably set to something smaller in php.ini on iguana. To fix the problem, it would need to be bumped up and apache would have to be kicked. The php.ini setting is in:
http://php.osuosl.org/manual/en/ini.php#ini.list
The setting is upload_max_filesize, and should be set to something higher -- maybe 12M? That should be up to sysadmins to determine what is feasible.
Assignee: morgamic → server-ops
Updated•19 years ago
|
Component: Developers → Server Operations
Product: Update → mozilla.org
Target Milestone: 1.0 → ---
Version: unspecified → other
Updated•19 years ago
|
Assignee: server-ops → polvi
Comment 3•19 years ago
|
||
Gecko is currently at 10MB, so I bumped it to 15MB. But this will probably not solve the issue.
Passing along the bug to someone more helpful.
Assignee: polvi → aravind
Comment 4•19 years ago
|
||
And by Gecko, I mean iguana, sorry for the confusion.
Assignee | ||
Comment 5•19 years ago
|
||
Tried bumping up the max size setting to 15 M. The request still times out with this message.
Requested content-length of 2251771 is larger than the configured limit of 1572864
Waiting for morgamic to test this out in a dev environment instead of tweaking stuff on a live system.
Assignee | ||
Comment 6•19 years ago
|
||
This document lists all the parameters that control the upload sizes.
http://www.squirrelmail.org/wiki/AttachmentSize
The settings I changed are:
in php.ini:
memory_limit = 20M
post_max_size = 15M
upload_max_filesize = 15M
and in php.conf (/etc/httpd/conf.d)
LimitRequestBody 15728640
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•