[
https://issues.apache.org/struts/browse/STR-2959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41246
]
Niall Pemberton commented on STR-2959:
--------------------------------------
We have generally been pretty careful about backwards incompatible changes
using deprecate/remove cycles giving users advance warning. I see no reason not
to follow that approach in this case - i.e. Add a new method that returns a
long and deprecate the old method. The answer to the question "why the original
one still exists" should of course be in the deprecation message (i.e. use the
new method). Changing the method signature will of course beg the question "why
did you break compatibility with 1.3 without warning?"
> File upload has 2GB limit
> -------------------------
>
> Key: STR-2959
> URL: https://issues.apache.org/struts/browse/STR-2959
> Project: Struts 1
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.7, 1.2.8, 1.2.9, 1.3.5
> Environment: Websphere Application Server 6.0
> Reporter: Richard Harding
> Priority: Minor
> Fix For: 1.4.0
>
>
> Struts currently has a 2GB limit on file upload.
> org.apache.struts.upload has an artificial limit of 2GB.
> org.apache.commons.fileupload does not have this limit since 'long' is used
> in place of 'int'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
