Hello all, There's a reasonably well-documented problem with IE6's interpretation of "Pragma: no-cache" and "Cache-control: no-cache" headers when served over SSL. IE6 will simply fail to complete the download because it determines that it shouldn't write the file to temporary space.
My question is: What's the best way to force my AppFuse application (or tomcat) to not append cache-control/pragma headers to one or more jsps (or other artifacts)? I've removed all cache-related headers (that are plainly evident) from my decorator pages. My understanding is that the headers are appended by tomcat5.5 (coyote?) itself. In my research, I've often encountered the suggestion of including: <Valve className="org.apache.catalina.authenticator.FormAuthenticator" disableProxyCaching="false" /> in the <context> of my context.xml. I've attempted this without much success, and I'm not sure FormAuthenticator is the correct class to use with an AppFuse application. I'm not familiar enough with valves to know how it'd work with AppFuse/Ageci/etc. I've written a filter that applies more appropriate headers to my ServletResponse's, but tomcat seems to insist on no-cache headers and ignore the ones I have set. Sadly, the only other commonly suggested fix that I have found, "tell your users not to use IE6", is something that probably wouldn't pass QA. Help? Thanks much. jeb -- View this message in context: http://www.nabble.com/IE6-SSL-%2B-no-cache-Problem-tp20235529s2369p20235529.html Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
