Any webkit / internal browser masters around?
by Rob Stryker
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
6 years, 7 months
ACTION REQUIRED: Reminder, code freeze for JBT 4.2.3.CR1 / JBDS 8.1.0.CR1 is tomorrow
by Nick Boldt
Please make sure you're using the latest 4.2.3.CR1-SNAPSHOT parent pom
in your builds, in order to pick up the latest 4.42.0.Final-SNAPSHOT
target platform.
If you've contributed fixes to 4.2.3.CR1 (since 4.2.3.Beta1) and your
job is NOT currently enabled, please remember to do so, or at least to
tell me so I can do so for you.
More nags tomorrow!
Cheers,
Nick
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
6 years, 7 months
ACTION REQUIRED: Preparing for 4.2.3.CR1 CF next week [Mar 12]
by Nick Boldt
Some steps need to be done to get ready for code freeze next week (March
12).
These are:
a) rename/rebuild parent pom, upversioned to 4.2.3.CR1 [done]
b) rename/rebuild target platform
c) update projects *which will have changes for CR1* to use this latest
parent pom
Rather than asking *everyone* to update their root pom and wasting your
time w/ Task JIRAs, I'd rather ask this:
* Which projects plan to contribute changes to 4.2.3.CR1?
If you have changes, please upversion your parent pom to use
4.2.3.CR1-SNAPSHOT.
If you do not, you need do nothing at this time.
If you would still like a Task JIRA next week, I can certainly create
them. Just let me know which project(s) need them and I'll skip sending
them to those who don't need them.
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
6 years, 7 months
