[tor-bugs] #15333 [Tor]: Minor control-spec.txt corrections.

[Tor Bug Tracker & Wiki]

#15333: Minor control-spec.txt corrections.
-------------------------+--------------------------------------
     Reporter:  yawning  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  trivial  |  Milestone:
    Component:  Tor      |    Version:  Tor: unspecified
   Resolution:           |   Keywords:  tor-spec, tor-controller
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+--------------------------------------

Comment (by yawning):

 Replying to [comment:1 special]:
 > Replying to [ticket:15333 yawning]:
 > > Re: SETCONF:
 > > >  Tor responds with a "250 configuration values set" reply on
 success.
 > > >  If some of the listed keywords can't be found, Tor replies with a
 > >
 > > According to git blame that hasn't been the case since... 2008?  2007?
 >
 > Do you mean that the text is different? Current tor responds with '250
 OK'.

 Indeed. It stood out as the only thing not documented to return `250 OK`.

 > > >  Sent from the client to the server.  The syntax is as for GETCONF:
 > > >    "GETINFO" 1*(SP keyword) CRLF
 > > >  one or more NL-terminated strings.  The server replies with an
 INFOVALUE
 > > >  message, or a 551 or 552 error.
 > >
 > > "one or nor NL-terminated strings" is confusing.  Did a newline and a
 word get cutoff somewhere, or am I just being dense?
 >
 > INFOVALUE also isn't defined or used anywhere else. Both of those issues
 date back to 2005.

 Yup.  Should figure out what it should say.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15333#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online