[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #535 [Tor Relay]: servers should support hearing "not new descriptor"
#535: servers should support hearing "not new descriptor"
--------------------------------+-------------------------------------------
Reporter: arma | Type: enhancement
Status: new | Priority: minor
Milestone: Tor: 0.2.3.x-final | Component: Tor Relay
Version: 0.2.0.8-alpha | Resolution: None
Keywords: | Parent:
--------------------------------+-------------------------------------------
Changes (by nickm):
* milestone: post 0.2.1.x => Tor: 0.2.3.x-final
Old description:
> 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]
New description:
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]
--
Comment:
Marking for 0.2.3.x-final.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/535#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs