11644 - Cache options based on file type

Status: RESOLVED INVALID

(Core :: Networking: Cache, enhancement)

Description

[luch]

There should a cache option that allows to choose what type of file should be
kept in cache.  You could put a couple of checkboxes:

|| HTML files
|| Images
|| Other files

This could be helpful for small intranet networks that don't want to keep
personnal info on disk (HTML Files) but that want to keep images to speed up
loading.

Thanx for at least reading and maybe apply! :)

Comment 1

[Gagan]

Good idea. Should be doable relatively easily in 5.0. But cache is not in yet.
Marking for later and assigning to scott- our Cache Man! :) Thanks for the
suggestion.

Comment 2

[Matthew Tuck [:CodeMachine]]

This could become a part of bug #7380, which would be a bit more flexible than
this.

Comment 3

[leger]

Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.

Comment 4

[shrirang khanzode]

Sorry for the spam, changing QA contact.

Comment 5

[Christopher Hoess (gone)]

LATER is deprecated.

Comment 6

[Bart van Bragt]

I think I'm missing the point of this bug..
If you don't want certain content to be cached then you can provide the browser
with the appropriate HTTP headers.

IMO not caching sensitive files is something that the server should manage, not
the client..

Comment 7

[Darin Fisher]

*** Bug 265092 has been marked as a duplicate of this bug. ***

Comment 8

[benc]

->defaults

Comment 9

[Darin Fisher]

-> default owner

Comment 10

[u7736]

+1 to Bart's comment... the server has a much better idea about what is cacheable than the user does. 

If this is about giving hints to the algorithm that is used when there isn't explicit freshness info (i.e., heuristic freshness), that's OK, but if it's about overriding the server's freshness info, it's going to cause a lot of trouble.

Comment 11

[benc]

RESOLVED/invalid.

Now that I've (finally) had time to read this entire bug, I'm going to mark it invalid, per my hypothetical powers as the default cacheQA person.

The reason: For the use case provided, this is something that should be implemented via the server. Doing this via a client is not a good idea, even if you have enterprise-level browser config features, like MCD. 

There might be other, sensible use cases that would fall under the description of this bug, but for now, this bug is closed.