Tomcat does remembers the original "POST data". I know because once a user successfuly sings in, the original "POST data" is available either from a jsp or servlet. The problem is that it is not available within the login.jsp page.
--- On Mon, 5/4/09, Caldarale, Charles R <chuck.caldar...@unisys.com> wrote: From: Caldarale, Charles R <chuck.caldar...@unisys.com> Subject: RE: How to make request parameters available to a login.jsp? To: "Tomcat Users List" <users@tomcat.apache.org> Date: Monday, May 4, 2009, 2:02 PM > From: André Warnier [mailto:a...@ice-sa.com] > Subject: Re: How to make request parameters available to a login.jsp? > > Except that it (usually) breaks down if the original request > was a POST. Because then, the server would have needed to > remember, not only the URI of the original request, but also > the content (body) of it, since it was made via a POST. > > I am willing to be impressed, but I don't think that Tomcat's > form-based authentication mechanism would be able to read the > original POST data, memorise it somewhere, and then "replay it" > when it gets the login form duly completed. You need to be impressed: Tomcat does exactly what you don't think it's able to. Read the servlet spec, and the doc for the maxSavePostSize attribute of the <Connector> element. http://tomcat.apache.org/tomcat-6.0-doc/config/http.html#Attributes - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
