Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348917 - Figure out a better way to manage dev-time browser caching of js, html, and css
Summary: Figure out a better way to manage dev-time browser caching of js, html, and css
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: Client (show other bugs)
Version: 0.2   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: 0.2   Edit
Assignee: Simon Kaegi CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 339605 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-06-09 11:28 EDT by Simon Kaegi CLA
Modified: 2011-09-01 11:42 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Kaegi CLA 2011-06-09 11:28:51 EDT 
This is slowly driving me nuts and is also a real problem when we go to update orion.eclipse.org.

We're currently just setting ETags and last modified headers. I'll try playing around with Cache-Control headers to see if we can do something better here. I think this is important especially as we get closer to the release as saying stuff like blow away your localStorage and browser cache are not at all ok.
Comment 1 Simon Kaegi CLA 2011-06-10 16:32:11 EDT 
Fixed in HEAD. John Reviewed.
Comment 2 Simon Kaegi CLA 2011-06-10 16:33:17 EDT 
*** Bug 339605 has been marked as a duplicate of this bug. ***