Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #23499
Closed (moved) (moved)
Open
Created Sep 13, 2017 by Roger Dingledine@arma

dir server responses should include a Date: header even when not responding 200

Catalyst noticed that when the Tor client fetches a consensus from moria1 but moria1 responds "302 Not modified", moria1 does not include a Date: header in that response. So a Tor client whose clock is wrong won't be told about it at this stage.

The fix is that all dir responses should include the Date: header, not just 200 responses.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking