We occasionally run into problems with users of our site who complain that they get erratic behaviour because their local corporate proxy server sends back cached versions of dynamic pages (jsp's), nevermind people who can't figure out their browser's cache settings. The obvious argument is that it's an issue with their proxy server, but, the customer being _always_ right and not willing to accept any problems on their end, we're trying to figure out a solution that works even through the most poorly configured proxy and browser. Any ideas?
The direction that looks most promising would be to put some random string within the URI instead of in the query string or to set no-cache headers (both of which particularly bad proxy servers might still ignore). So if we could generate links and form actions like: http://foo.com/ourAppContext/everchangingtotallyrandomstring/someAction.do it be good, where the random string is different for every generated link and form action. So using extension mappings in web.xml we can send all *.do's, e.g. the above example, to the ActionServlet, but when Struts tries to find an action mapping, it's looking for: /everchangingtotallyrandomstring/someAction.do which it obviously won't find. So my first thought is to extend the ActionServlet to have it only look up an action mapping using the URI after the lastIndexOf '/'. Then the next issue a consistent way to generate those types of links without convoluted changes to existing JSP's, so maybe something like extend LinkTag. Thoughts? Thanks, david --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
