Closed
Bug 278350
Opened 21 years ago
Closed 19 years ago
tinderbox's showlog should send cache headers
Categories
(Webtools Graveyard :: Tinderbox, defect)
Webtools Graveyard
Tinderbox
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Biesinger, Assigned: cls)
References
()
Details
Attachments
(1 file)
|
1.89 KB,
patch
|
bear
:
review+
|
Details | Diff | Splinter Review |
since a build log never changes, it would be nice to send an Expires: header far
in the future, so that the browser can cache it. probably also a last-modified
header for when the log was created.
| Reporter | ||
Updated•21 years ago
|
For the most part, the logs are static so they should be cached. If someone wants to see an updated tinderbox comment, they are probably more likely to click on the star and get the pop-up window rather than reload the entire multi-megabyte log.
This patch replaces the expires meta tag with Last-Modified & Expires headers. The logs are set to expire 1 hour from when the page is loaded.
Comment on attachment 224497 [details] [diff] [review]
v1.0
Hrm. By checking the timestamp on the notes.txt, the cgi will cause all logs to show as updated whenever anyone adds any comment. I don't like that but fixing it may require us to read & store the value of the notes before generating the last-mod date instead of doing everything on the fly as it currently does.
Updated•19 years ago
|
Attachment #224497 -
Flags: review?(bear) → review+
/cvsroot/mozilla/webtools/tinderbox/showlog.cgi,v <-- showlog.cgi
new revision: 1.20; previous revision: 1.19
done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•