aboutsummaryrefslogtreecommitdiff
path: root/bandwidth-file-spec.txt
diff options
context:
space:
mode:
authorteor <teor@torproject.org>2019-03-06 09:36:43 +1000
committerNick Mathewson <nickm@torproject.org>2019-03-08 10:29:14 -0500
commit8d7d1a7ea1a1a0efed64ad3f146b2c82f00ce7d6 (patch)
tree12f03c87de25d333d4cbe66b0db31dde6e5834ad /bandwidth-file-spec.txt
parentb8ca52cc89b90d07d961841b9e18440548407ad4 (diff)
downloadtorspec-8d7d1a7ea1a1a0efed64ad3f146b2c82f00ce7d6.tar.gz
torspec-8d7d1a7ea1a1a0efed64ad3f146b2c82f00ce7d6.zip
bandwidth-file: Clean up trailing spaces in the text file
Diffstat (limited to 'bandwidth-file-spec.txt')
-rw-r--r--bandwidth-file-spec.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt
index 7192527..556aa8c 100644
--- a/bandwidth-file-spec.txt
+++ b/bandwidth-file-spec.txt
@@ -58,7 +58,7 @@
bandwidth values (averages and descriptor bandwidths).
All Tor versions can consume format version 1.0.0.
-
+
All Tor versions can consume format version 1.1.0 and later,
but Tor versions earlier than 0.3.5.1-alpha warn if the header
contains any KeyValue lines after the Timestamp.
@@ -310,10 +310,10 @@
In version 1.0.0, Header List ends when the first relay bandwidth
is found conforming to the next section.
-
+
Implementations of version 1.1.0 and later SHOULD use a 5-character
terminator.
-
+
Tor 0.4.0.1-alpha and later look for a 5-character terminator,
or the first relay bandwidth line. sbws versions 0.1.0 to 1.0.2
used a 4-character terminator, this bug was fixed in 1.0.3.