From jira-events at lists.jboss.org Wed Sep 28 08:36:26 2011 Content-Type: multipart/mixed; boundary="===============3335974739775574055==" MIME-Version: 1.0 From: Jean-Pierre Schmit (JIRA) To: richfaces-issues at lists.jboss.org Subject: [richfaces-issues] [JBoss JIRA] Commented: (RF-6906) FileUpload: full file transfer happens if size limit is exceeded Date: Wed, 28 Sep 2011 08:36:26 -0400 Message-ID: <156791447.83878.1317213386641.JavaMail.tomcat@jira02.app.mwc.hst.phx2.redhat.com> In-Reply-To: 31996116.1240428442470.JavaMail.jira@cloud.prod.atl2.jboss.com --===============3335974739775574055== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/RF-6906?page=3Dcom.atlassian.jira.plu= gin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12631026#comm= ent-12631026 ] = Jean-Pierre Schmit commented on RF-6906: ---------------------------------------- We can reproduce this issue. Our findings are that if a POST request with an attachment indicates throug= h a header content-length a size that is bigger than the maximum that is co= nfigured at server side, the server replies to the POST request with = The problem is that the browser does not seem to read this response and goe= s on posting the entire attachment. In the browser, you do not see the resp= onse 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 happ= ens 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 =20 --===============3335974739775574055==--