diff options
Diffstat (limited to 'spec/control-spec/replies.md')
| -rw-r--r-- | spec/control-spec/replies.md | 46 |
1 files changed, 23 insertions, 23 deletions
diff --git a/spec/control-spec/replies.md b/spec/control-spec/replies.md index c55635c..c7b1ab7 100644 --- a/spec/control-spec/replies.md +++ b/spec/control-spec/replies.md @@ -121,11 +121,11 @@ Tor 0.2.2.x and later), then each event line as specified below may be followed by additional arguments and additional lines. Additional lines will be of the form: -"650" ("-"/" ") KEYWORD ["=" ARGUMENTS] CRLF +"650" ("-"/" ") KEYWORD \["=" ARGUMENTS\] CRLF Additional arguments will be of the form -SP KEYWORD ["=" ( QuotedString / * NonSpDquote ) ] +SP KEYWORD \["=" ( QuotedString / * NonSpDquote ) \] Clients MUST tolerate events with arguments and keywords they do not recognize, and SHOULD process those events as if any unrecognized @@ -542,9 +542,9 @@ The syntax is: Num = 1*DIGIT ``` -BytesRead and BytesWritten are the totals. [In a future Tor version, +BytesRead and BytesWritten are the totals. \[In a future Tor version, we may also include a breakdown of the connection types that used -bandwidth this second (not implemented yet).] +bandwidth this second (not implemented yet).\] <a id="control-spec.txt-4.1.5"></a> @@ -615,7 +615,7 @@ Syntax: Error and UTCExpiry are only provided if extended events are enabled. The values for Error are mostly useless. Future values will be -chosen to match 1*(ALNUM / "_"); the "Unable to launch resolve request" +chosen to match 1\*(ALNUM / "\_"); the "Unable to launch resolve request" value is a bug in Tor before 0.2.4.7-alpha. Expiry is expressed as the local time (rather than UTC). This is a bug, @@ -632,7 +632,7 @@ the address was resolved. ### Descriptors uploaded to us in our role as authoritative dirserver -[NOTE: This feature was removed in Tor 0.3.2.1-alpha.] +\[NOTE: This feature was removed in Tor 0.3.2.1-alpha.\] Tor generates this event when it's a directory authority, and somebody has just uploaded a server descriptor. @@ -662,7 +662,7 @@ Syntax: "650" SP "DESCCHANGED" CRLF -[First added in 0.1.2.2-alpha.] +\[First added in 0.1.2.2-alpha.\] <a id="control-spec.txt-4.1.10"></a> @@ -1151,7 +1151,7 @@ The Status values are: Syntax: -"650" "+" "NS" CRLF 1*NetworkStatus "." CRLF "650" SP "OK" CRLF +"650" "+" "NS" CRLF 1\*NetworkStatus "." CRLF "650" SP "OK" CRLF The event is used whenever our local view of a relay status changes. This happens when we get a new v3 consensus (in which case the entries @@ -1159,7 +1159,7 @@ we see are a duplicate of what we see in the NEWCONSENSUS event, below), but it also happens when we decide to mark a relay as up or down in our local status, for example based on connection attempts. -[First added in 0.1.2.3-alpha] +\[First added in 0.1.2.3-alpha\] <a id="control-spec.txt-4.1.13"></a> @@ -1243,7 +1243,7 @@ every relay in the consensus. NEWCONSENSUS is a separate event from the NS event, because the list here represents every usable relay: so any relay *not* mentioned in this list is implicitly no longer recommended. -[First added in 0.2.1.13-alpha] +\[First added in 0.2.1.13-alpha\] <a id="control-spec.txt-4.1.16"></a> @@ -1285,7 +1285,7 @@ of build times Tor stores (NCIRCUITS_TO_OBSERVE). The Timeout itself is provided in milliseconds. Internally, Tor rounds this value to the nearest second before using it. -[First added in 0.2.2.7-alpha] +\[First added in 0.2.2.7-alpha\] <a id="control-spec.txt-4.1.17"></a> @@ -1309,7 +1309,7 @@ semantics of the signals here. Note that the HALT (SIGTERM) and SHUTDOWN (SIGINT) signals do not currently generate any event. -[First added in 0.2.3.1-alpha] +\[First added in 0.2.3.1-alpha\] <a id="control-spec.txt-4.1.18"></a> @@ -1317,7 +1317,7 @@ generate any event. The syntax is: -StartReplyLine *(MidReplyLine) EndReplyLine +StartReplyLine \*(MidReplyLine) EndReplyLine ```text StartReplyLine = "650-CONF_CHANGED" CRLF @@ -1356,7 +1356,7 @@ purpose. Other fields are as specified in section 4.1.1 above. -[First added in 0.2.3.11-alpha] +\[First added in 0.2.3.11-alpha\] <a id="control-spec.txt-4.1.20"></a> @@ -1407,7 +1407,7 @@ These events are generated about once per second per connection; no events are generated for connections that have not read or written. These events are only generated if TestingTorNetwork is set. -[First added in 0.2.5.2-alpha] +\[First added in 0.2.5.2-alpha\] <a id="control-spec.txt-4.1.22"></a> @@ -1477,12 +1477,12 @@ These events are generated about once per second per circuit; no events are generated for circuits that had no attached stream writing or reading. -[First added in 0.2.5.2-alpha] +\[First added in 0.2.5.2-alpha\] -[DELIVERED_READ, OVERHEAD_READ, DELIVERED_WRITTEN, and OVERHEAD_WRITTEN -were added in Tor 0.3.4.0-alpha] +\[DELIVERED_READ, OVERHEAD_READ, DELIVERED_WRITTEN, and OVERHEAD_WRITTEN +were added in Tor 0.3.4.0-alpha\] -[SS, CWND, RTT, and MIN_RTT were added in Tor 0.4.7.5-alpha] +\[SS, CWND, RTT, and MIN_RTT were added in Tor 0.4.7.5-alpha\] <a id="control-spec.txt-4.1.23"></a> @@ -1554,7 +1554,7 @@ These events are generated about once per second per circuit; no events are generated for circuits that have not added or processed any cell. These events are only generated if TestingTorNetwork is set. -[First added in 0.2.5.2-alpha] +\[First added in 0.2.5.2-alpha\] <a id="control-spec.txt-4.1.24"></a> @@ -1603,7 +1603,7 @@ at LastRefill in order not to report empty times more than once. These events are only generated if TestingTorNetwork is set. -[First added in 0.2.5.2-alpha] +\[First added in 0.2.5.2-alpha\] <a id="control-spec.txt-4.1.25"></a> @@ -1714,8 +1714,8 @@ takes to fetch something over the Tor network. This can be between a couple of seconds up to 60 seconds (not a hard limit). But, in any cases, this event will reply either the descriptor's content or an empty one. -[HS_DESC_CONTENT was added in Tor 0.2.7.1-alpha] -[HS v3 support added 0.3.3.1-alpha] +\[HS_DESC_CONTENT was added in Tor 0.2.7.1-alpha\] +\[HS v3 support added 0.3.3.1-alpha\] <a id="control-spec.txt-4.1.27"></a> |