Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #26131

Closed (moved)
Open
Opened May 18, 2018 by teor@teor

Add an Expires header to consensus-health

Sometimes I get really stale (9 hours old) cached consensus-health pages. This happens because the page doesn't say when it expires, or what it's maximum age is. So my browser guesses that it can be cached for multiple hours.

Please add an "Expires" header to consensus-health, set to a few minutes after the scheduled time of the next job. We could also add a max-age of slightly more than an hour.

Here is the relevant HTTP spec: https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.2.4

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#26131