</attribute>
<attribute name="swallowAbortedUploads" required="false">
- <p>Set to false if Tomcat should <b>not</b> read any additional
- request body data for aborted uploads and instead abort the client
- connection. This setting is used in the following situations:
+ <p>Set to false if Tomcat should <b>not</b> read any additional request
+ body data for aborted uploads and instead abort the client connection.
+ This setting is used in the following situations:
<ul>
<li>the size of the request body is larger than the
- <code>maxPostSize</code> configured in the connector
- </li>
- <li>the size limit of a MultiPart upload is reached
- </li>
- <li>the servlet sets the response status to 413
- (Request Entity Too Large)
- </li>
+ <code>maxPostSize</code> configured in the connector</li>
+ <li>the size limit of a MultiPart upload is reached</li>
+ <li>the servlet sets the response status to 413 (Request Entity Too
+ Large) </li>
</ul>
Not reading the additional data will free the request processing thread
more quickly. Unfortunately most HTTP clients will not read the response
- in case they can not write the full request.</p>
- <p>The default is <code>true</code>, so additional data is being read.</p>
+ if they can not write the full request.</p>
+ <p>The default is <code>true</code>, so additional data will be
+ read.</p>
+ <p>Note if an error occurs during the request processing that triggers
+ a 5xx response, any unread request data will always be ignored and the
+ client connection will be closed once the error response has been
+ written.</p>
</attribute>
<attribute name="swallowOutput" required="false">