loggerhead could mark all pages cacheable
Bug #567729 reported by
Martin Pool
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| loggerhead |
Triaged
|
Low
|
Max Kanat-Alexander | ||
| loggerhead-breezy |
Triaged
|
Low
|
Unassigned | ||
Bug Description
It might be nice if Loggerhead had an option to mark all pages as cachable with an expiry of say 10m. This could be simpler than (but complementary to) doing etag based revalidation. Eventually for pages that should never change, like the contents of a particular historical file or revision we could allow much longer caching.
Launchpad could then run a caching reverse proxy in front of codebrowse.
| Changed in loggerhead: | |
| assignee: | nobody → Max Kanat-Alexander (mkanat) |
Revision history for this message
| Martin Pool (mbp) wrote Re: [Bug 567729] Re: loggerhead could mark all pages cacheable | #1 |
Revision history for this message
| Max Kanat-Alexander (mkanat) wrote | #2 |
Revision history for this message
| Robert Collins (lifeless) wrote | #3 |
| Changed in loggerhead: | |
| status: | Confirmed → Triaged |
| importance: | Medium → Low |
| Changed in loggerhead-breezy: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
To post a comment you must log in.
This would actually be quite nice for Launchpad, if you'd care to work
on it Max.
--
Martin