Chhaya Patil wrote:When i deploy my Struts2 application on Weblogic server; for the first time when the user logs in automatically ;jsessionid=<some value> is put in URL.
The problem is that the web server does not like ; and it gives 403- forbidden page error.
jsessionid is used when your browser doesn't support cookie and comes into a play when you create a session.
Chhaya Patil wrote:I had no such issue with Struts 1 applications before. Is there a way to stop Struts from putting that jsesionid in URL?
May be your doing something wrong with the way S2 action defined, as S2 has different config than S1.