Hey all: The internal browser view / browser editor when using WebKit (and Snjezana indicates other internal browser implementations as well) seems to be caching requests that they shouldn't. The interesting thing here is that BrowserViewer (used in both editor and view) are passing in "Cache-Control: no-cache" into the request, and yet the results are still being cached. This seems to indicate that the underlying WebKit is ignoring this flag for some reason. https://issues.jboss.org/browse/JBIDE-18685 https://bugs.eclipse.org/bugs/show_bug.cgi?id=448933 Is anyone experienced enough in the underlying APIs that can assist here in debugging or finding what in WebKit (or other browsers) is going wrong that they're ignoring this flag? w3.org documentation indicates these flags should *never* be ignored: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html 14.9 Cache-Control The Cache-Control general-header field is used to specify directives that MUST be obeyed by all caching mechanisms along the request/response chain. The directives specify behavior intended to prevent caches from adversely interfering with the request or response. These directives typically override the default caching algorithms. Cache directives are unidirectional in that the presence of a directive in a request does not imply that the same directive is to be given in the response. This could be a bug in webkit, or in how the internal browser is communicating with webkit, but I seem to be out of my area of expertise trying to drill down into the JNI commands and webkit proper. Anyone have any ideas or experience in this area? - Rob Stryker _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev