Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326215

Summary: [Webapp] Needs more flexible to control which pages need to cache
Product: [Eclipse Project] Platform Reporter: jon <czhuang>
Component: User AssistanceAssignee: platform-ua-inbox <platform-ua-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: annette_s_riffe, benysh, cgold, czhuang, liggitt
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description jon CLA 2010-09-24 22:48:50 EDT 
Build Identifier: 3.4

Can the pages be delivered with a "don't cache this ever" header?  Without this, the browser decides whether to cache it or not.  We were running into problems where we'd change languages and the content would show up in the previous language while the titles and labels were displayed in the new language.

That was actually the major complaint I had - - many of our clients deploy with caching proxy servers.  From what I saw the IEHS responses lacked any cache controls.  Some servers cache all pages that lack cache controls.



Reproducible: Always

Steps to Reproduce:
1. Start Eclipse Help System
2. Open the browser and visit the help system
3. All pages cached in the proxy server
Comment 1 Chris Goldthorpe CLA 2010-09-28 14:16:47 EDT 
The root of the problem is that Eclipse uses the same URL to represent content pages in different languages. This is a problem because caching is allowed to be performed by either the server or client if the URL is identical and there is nothing in the header to indicate that caching should not be performed. This only affects infocenters which serve content in more than one language.

I can see two possible solutions.

a) Add a content filter which adds cache control headers to all content pages. This may be the quickest way to solve the immediate problem in that it would not require a new version of Eclipse, a bundle containing the content filter could be added to the infocenter. This would work for html and xhtml files but would not solve the problem of image and css files which differ by locale.

b) A better solution which would require more work would be to use different urls for the different locales, so that a url such as http://host/help/topic/plugin/path.htm would become something like http://host/help/nltopic/fr/plugin/path.htm if the topic was known to be in french. The EclipseConnector would handle reading the correct file. This would require the toc and index views to change their hyperlinks to add in the locale.

If we pick either of these solutions the work would need to be scheduled, currently this is not in the plan for Eclipse 3.7.
Comment 2 Chris Goldthorpe CLA 2010-09-28 14:17:45 EDT 
*** Bug 326198 has been marked as a duplicate of this bug. ***
Comment 3 Lars Vogel CLA 2019-11-14 02:16:34 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.