This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9338 - Why can't I have the resource files (CSS file, images, JavaScript files) be cached without caching the whole page? I hacn't have a different HTML tag for just the sign-on page, and the other pages need to not be cached due to private, frequently changing
Summary: Why can't I have the resource files (CSS file, images, JavaScript files) be c...
Status: RESOLVED NEEDSINFO
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-26 14:53 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-03-26 14:53:18 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#the-history-interface

Comment:
Why can't I have the resource files (CSS file, images, JavaScript files) be
cached without caching the whole page? I hacn't have a different HTML tag for
just the sign-on page, and the other pages need to not be cached due to
private, frequently changing financial information on them. I would like the
user to to able to be able to get the advatages of the cache from whatever
page they are on when they save the cache, but the only HTML to cache should
be the sign on page.

Posted from: 67.188.133.45
Comment 1 Ian 'Hixie' Hickson 2010-04-02 06:09:12 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: I don't understand. Which cache? I don't see anything in the specified section that would be relevant here. Do you mean what is commonly referred to as the bfcache?