Configure Max File Size for 1 Action

[David Sujista]

I have one struts 2.3 action which should be permitted to have very large file uploads and all of the other actions have a much smaller max file upload limit.

The first thing that I tried was adding the following to the action:

        <action name="myAction" class="MyAction">
            <interceptor-ref name="defaultStack">
                    <param name="maximumSize">524288000</param>
                    <param name="fileUpload.maximumSize">524288000</param>
                    <param name="struts.multipart.maxSize">524288000</param>           
            </interceptor-ref>
        </action>

However, my 2 MB test file was still rejected as being too large (the large number as a parameter is 500 MB).

The next thing that I tried was defining a completely new interceptor-stack like this:

<interceptor-stack name="fileUploads">
                <interceptor-ref name="exception"/>
                <interceptor-ref name="alias"/>
                <interceptor-ref name="servletConfig"/>
                <interceptor-ref name="prepare"/>
                <interceptor-ref name="i18n"/>
                <interceptor-ref name="chain"/>
                <interceptor-ref name="debugging"/>
                <interceptor-ref name="profiling"/>
                <interceptor-ref name="scopedModelDriven"/>
                <interceptor-ref name="modelDriven"/>
                <interceptor-ref name="fileUpload">
                    <param name="maximumSize">524288000</param>
                    <param name="fileUpload.maximumSize">524288000</param>
                    <param name="struts.multipart.maxSize">524288000</param>
                </interceptor-ref>
                <interceptor-ref name="checkbox"/>
                <interceptor-ref name="staticParams"/>
                <interceptor-ref name="params">
                  <param name="excludeParams">dojo\..*</param>
                </interceptor-ref>
                <interceptor-ref name="conversionError"/>
                <interceptor-ref name="validation">
                    <param name="excludeMethods">input,back,cancel,browse</param>
                </interceptor-ref>
                <interceptor-ref name="workflow">
                    <param name="excludeMethods">input,back,cancel,browse</param>
                </interceptor-ref>
            </interceptor-stack>

I then switched the action to use this interceptor-stack:

        <action name="myAction" class="MyAction">
            <interceptor-ref name="fileUploads">
            </interceptor-ref>
        </action>

However, my 2 MB test file was still rejected for being too large. The rejection was by Struts - not tomcat or the web server. I get the following struts action error:

"Request exceeded allowed size limit! Max size allowed is: 2,097,152 but request was: 2,631,140!"

Does anyone see what I did wrong in the configuration? Or how I should configure struts to let one action upload large files?

Thanks!

[Joe Ess]

The way I understand it, to set the maximum upload size and maximum file size for the entire application, one would declare (for a 1GB limit):

    <!-- the maximum size of a upload request -->
    <constant name="struts.multipart.maxSize" value="1073741824" />
    <!-- maximum size of an individual file-->
    <constant name="struts.multipart.maximumSize" value="1073741824" />

If you were going to configure the interceptor, the documentation says to do the following:

    <action name="doUpload" class="com.example.UploadAction">
        <interceptor-ref name="basicStack"/>
        <interceptor-ref name="fileUpload">
            <param name="maximumSize">500000</param>
        </interceptor-ref> 
        <interceptor-ref name="validation"/>
        <interceptor-ref name="workflow"/>
 
        <result name="success">good_result.jsp</result>
    </action>

Note that the interceptor does not have properties named fileUpload.maximumSize (I've never seen that one) or struts.multipart.maximumSize (which is a Struts property, not an interceptor property)
I don't know for certain that doing both would allow the action to override the global setting, but the documentation seems to say that it can.