Hello Martin, first of all, the application works fine again - and I think, the application didn't had any problem ... see below.
Martin Gainty wrote: > Andreas- > > <Context cookies = "true"> Set to true if you want cookies to be used > for session identifier communication if supported by the client (this > is the default). Set to false if you want to disable the use of cookies > for session identifier communication, and rely only on URL rewriting by > the application. > > --so when you move to the new server and take the default you are using > cookies in lieu of URL rewrite I took the whole installation to the new server - therefore, using of cookies wasn't able, too. > OldServer If you are using rewrite which Apache server is handling the > re-writing and how is this implemented? I don't use any apache server - I'm just using tomcat with nothing else. The URL-rewriting is done automatically - I didn't do anything besides the definition in webapps/application/META-INF/context.xml. But I think I do know the problem meanwhile: I started a 4 th tomcat-session on the machine, a plain tomcat installation and run struts-blank. During tracing (with ethereal) my "broken" application, I could see a session cookie (-> jsessionid) in the header, sent from the browser to the server when the login-page has been started. But there isn't sent any rewritten URL back to the client after a successful login and no correct cookie either. After restarting the browser and therefore the deletion of the wrong cookie, the login did work fine again. I think there is a problem in struts / jsp wherever with the handling of cookies and or URL-rewriting. Somebody out there, who knows more about the implementation of the session handling with cookies and/or URL rewriting? Kind regards, Andreas Hartmann --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
