URL rewriting doesn't work http->https (blame the Servlet spec :). However, cookie sessions should be preserved (unless it is the browser that is choosing to not send the cookie). If it was my app, the first thing that I would try is to enable the RequestDumperValve to see if the cookie is actually being sent.
The log message is probably a red-herring. It is just logging that the Response has been reset (normal for error-pages and sendRedirects). Since the cookie should have been set on a Request prior to the one generating the reset, this shouldn't be a problem. Of course (as always :), if you can produce a simple war file that demonstrates this problem, by all means attach it to a bug-report at http://nagoya.apache.org/bugzilla. I'd be very interested to look at it ;-). "Peter T. Abplanalp" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > hi all, > > i have a tomcat 4.1.27 instance fronted by an instance of > apache 2.0.40, using jk2. it is a commerce site and at the > point of credit card information collection goes from http > to https. the first time a user goes from http to https, > the session information is lost (i.e. the order information) > but if the user uses https from the beginning, eveything is > fine. the specific error i am seeing is: > > org.apache.jk.server.JkCoyoteHandler action > INFO: RESET > > i have done some searching on the web for this error but > nothing i have found really helps. most responses to such > questions say something like, it is just an info type > message and can thus be ignored but the large issue of > session loss isn't addressed. > > does anyone have any idea what is going on here or have any > suggestions? > > thanks in advance for any and all assistance. > > -- > Peter Abplanalp > PGP: pgp.mit.edu --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
