Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 316
    • Issues 316
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #535
Closed
Open
Created Oct 24, 2007 by Roger Dingledine@armaReporter

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
Time tracking