You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/14 01:53:51 UTC

[jira] [Resolved] (SLING-2257) File uploads > 2GB are not available as request parameters

     [ https://issues.apache.org/jira/browse/SLING-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Norman resolved SLING-2257.
--------------------------------

       Resolution: Fixed
    Fix Version/s: Engine 2.2.6

Thanks for reporting this issue.

It is fixed in revision 1201565 by removing the embedded commons-fileupload classes from the engine bundle and importing the same classes from the org.apache.commons.fileupload (v1.2.2) bundle.

Please verify that this change solves the problem for your use case.
                
> File uploads > 2GB are not available as request parameters
> ----------------------------------------------------------
>
>                 Key: SLING-2257
>                 URL: https://issues.apache.org/jira/browse/SLING-2257
>             Project: Sling
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: Engine 2.2.0
>            Reporter: Dominique Pfister
>            Assignee: Eric Norman
>             Fix For: Engine 2.2.6
>
>
> When doing a file upload with a file size exceeding 2GB:
> curl -F "my_file=@a_very_large_file" --header "Content-Type: multipart/related; type=application/atom+xml" http://...
> the following server code snippet:
> <%
> org.apache.sling.api.request.RequestParameter fileParam = slingRequest.getRequestParameter("my_file");
> %>
> will report a "null" fileParam. Reason for this is a limitation in commons-fileupload-1.1.1 which is embedded in sling-engine: the servlet container will report a content length of -1 (as the size is not representable in an integer) and FileUploadBase.parseRequest then throws an "UnknownSizeException". This was fixed in commons-fileupload-1.2.1.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira