Tom Cook wrote: > Hi, > > I have spent hours trying to figure this out and have searched the bug > database and the mailing list archives, and have not had any luck, so > I am posting it here. > > The story: > > * I am building a web application using tomcat and struts. > * This application is a simple, four-form system, with one form > following another. Forms are JSPs. > * Everything works using an HTTP connector. > * Everything works using an HTTPS connector and lynx or IE. > > Now the story gets strange. When I use mozilla or netscape for linux, > or netscape for NT, the first two forms function correctly but the > third does not. Viewing the page source shows that the browser is > receiving the HTML correctly, but is not displaying it. Netscape 4.x > on NT says 'Connection reset by peer.' There are no errors in any of > the tomcat logs. > > If I try a GET request for the third form (ie. type its URL into the > address bar of a browser) then it is displayed correctly. It is only > when I try to get it by submitting another form that things go wrong. > This form has its method set to POST. > > This third form does not involve any struts actions or actionforms. > It is a JSP, and the form on the previous page has its 'action' > property set to the JSP URL, not an action. > > This problem persists even if I cut the third form down to this: > > <html><head>Hello</head><body>Hello.</body></html> > > My conclusion is that the SSL connector is probably setting the > Content-Length header incorrectly, causing browsers that look at that > header to expect more content than is actually being sent, hence the > 'Connection reset by peer' message despite the HTML being received > correctly.
SSL is done at a layer lower than HTTP, so Tomcat handles HTTPS exactly the same way as HTTP (in particular, content-length handling is the same). Try Tomcat 4.1.10. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
