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
  • #535

Closed (moved)
Open
Opened Oct 24, 2007 by Roger Dingledine@arma

servers should support hearing "not new descriptor"

Directory authorities, when they get a descriptor that isn't new enough (more than cosmetically different) right now send back a 200 response code.

We should send some different code, so servers have a chance of knowing whether their uploaded descriptor actually "took" or was silently discarded.

So, changes as I understand them: A) Tor servers should accept 200-299 as successes, not just 200.

B) What success code, within the range 201-299, most closely resembles "I accepted it but it wasn't new enough so I didn't use it"? Is there any precedent to follow here?

C) Once step A is done, authorities can start sending back other codes.

D) Is there any way to speed up reaching step C?

E) Should we also change 400 to a range 400-499?

[Automatically added by flyspray2trac: Operating System: All]

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