>From: "Roberto Flores" <[EMAIL PROTECTED]> > > If I manually take out the ;jsessionid=132mksvl213:-1 from the url the > action is found (but the session is lost of course). > > There's something wrong with the URL parser but I don't know what it is or > if it's a struts or websphere problem/ >
You must be going thru a webserver that dispatches to your application server? If so, I'd try republishing the config file the webserver plugin uses. In WAS 6 the server will push the config to the webserver but in WAS 5 you have to copy it to the server depending on the setup. If you are going directly to the application server, it might be a problem with the virtual host mappings. What port are you using (http://myhost:9080/xxx/xxx.do)? What version of WAS are you using? Gary > 2007/1/15, Gary VanMatre : > > > > >From: "Roberto Flores" > > > > > > Greetings, > > > > > > I can't use cookies since this app is for cellphones. On Tomcat there's > > no > > > problem, but in WebSphere enabling only url-rewriting causes 404 errors > > on > > > every page transition. > > > > > > Upon further inspection, the jsessionid values generated by WebSphere > > are > > > drastically different than the ones used by Tomcat: > > > > > > WebSphere (form) > > > ...action="/mo/HT40121.do;jsessionid=0000XwB08FgkQm4GzTCmLGT7jU4:-1"> > > > > > > > > > The last part of the jsessionid ":-1" represents the server you are pinned > > to if you have > > a clustered environment. The web-server plug-in will try to send you to > > the same server > > where your session was initially established. > > > > > > > Tomcat (form) > > > ...action="/mo/HT40121.do;jsessionid=CBDCF468D0874528995F835F16A2BF30 > > > > > > Clicking the submit button returns a 404. It seems the jsessionid is not > > > being parsed at all. > > > > > > Can you tell me if this is a configuration problem in either the Struts > > side > > > or WebSphere? > > > > > > > > > Do you think the 404 is because it is unable to find an action or a JSP > > page that the action is > > forwarding to? My guess is that it is a relative path problem were you > > are missing a html:base > > tag in your header. Just a guess... > > > > > > > > > Thanks for any help. > > > > > > Gary > >
