On 8/30/07, Eric Hermanson <[EMAIL PROTECTED]> wrote:
> exception. However, the exception isn't getting *processed* until
> AFTER all of the data is read. This is because of what appears to be
> a bug in MultipartStream.ItemInputStream.close().
Ah, I undestand now. It's not a bug, it's a ... mo
As I mentioned, the LimitedInputStream *IS* correctly raising the
exception. However, the exception isn't getting *processed* until
AFTER all of the data is read. This is because of what appears to be
a bug in MultipartStream.ItemInputStream.close(). After the
LimitedInputStream correctl
On 8/30/07, Eric Hermanson <[EMAIL PROTECTED]> wrote:
> setFileSizeMax is apparently intended to prevent the file upload if
> the file about to be uploaded is larger than a given size. However,
> the exception does not get processed until AFTER the entire file is
> uploaded to the server (thereby
setFileSizeMax is apparently intended to prevent the file upload if
the file about to be uploaded is larger than a given size. However,
the exception does not get processed until AFTER the entire file is
uploaded to the server (thereby defeating the purpose of the limit).
I went into the
