NAFAIK, but that's by no means definitive. I *do* know that you can configure a TC context (or default context) to do the opposite. In other words, turn off cookies and only use rewriting.
Hm, what if you create a filter to wrap the response with an HttpServletResponseWrapper that no-ops encodeUrl and encodeURL? Quoting Brice Ruth <[EMAIL PROTECTED]>: > Is there any way to disable URL rewriting (with jsessionid) in Tomcat or > via struts-config.xml or anything? I'm about at my wits end with this > jsessionid thing - now our search engine which indexes by crawling the > site (and doesn't support cookies) can't index properly because of the > jsessionid property ... and frankly, I'm not really caring at this point > if the 3-5% of visitors to our site can't use sessions (there's > practically no functionality that depends on it anyway - mainly a > performance improvement, where it is being used). I'd like to leave > sessions via cookies enabled, but disable URL rewriting for sessions. > > -- > Brice D. Ruth > Sr. IT Analyst > Fiskars Brands, Inc. -- Kris Schneider <mailto:[EMAIL PROTECTED]> D.O.Tech <http://www.dotech.com/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
