[
https://issues.jboss.org/browse/RF-6906?page=com.atlassian.jira.plugin.sy...
]
Jean-Pierre Schmit commented on RF-6906:
----------------------------------------
We can reproduce this issue.
Our findings are that if a POST request with an attachment indicates through a header
content-length a size that is bigger than the maximum that is configured at server side,
the server replies to the POST request with
<html id="_richfaces_file_upload_size_restricted"></html>
The problem is that the browser does not seem to read this response and goes on posting
the entire attachment. In the browser, you do not see the response to this request until
either
- all the data was posted and the browser sees the answer
- the browser realized that the underlying connection was terminated
Hence you do not see the response in tools like HttpFox or Chrome Developer tools.
We found in the Apache logs that the request is answered immediately.
It should be the same behavior on any installation.
We also have a configuration where Tomcat is behind an Apache installation and if you
upload a file of more than 20 Mb, Chrome (!) freezes and must be restarted, which was the
beginning of our investigation.
The latter point seems to concern only our installation.
FileUpload: full file transfer happens if size limit is exceeded
----------------------------------------------------------------
Key: RF-6906
URL:
https://issues.jboss.org/browse/RF-6906
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: base functionality , component-input
Affects Versions: 3.3.1
Reporter: Nick Belaevski
Fix For: 4.Future
If file upload component is not using Flash, then full file transfer happens if file size
is greater than allowed maximum
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira