aboutsummaryrefslogtreecommitdiff
path: root/changes
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-03-25 17:11:04 -0400
committerNick Mathewson <nickm@torproject.org>2011-03-25 18:32:28 -0400
commit550749555cd57a1f82fe6c08e866ae14456ed439 (patch)
treec2d417f7d58d308b0c9c75875ee320c0a244bcb9 /changes
parentdddd333a80ee2e9bb731cb3c127ace3741d49673 (diff)
downloadtor-550749555cd57a1f82fe6c08e866ae14456ed439.tar.gz
tor-550749555cd57a1f82fe6c08e866ae14456ed439.zip
Remove workaround code for bug539
We fixed bug 539 (where directories would say "503" but send data anyway) back in 0.2.0.16-alpha/0.1.2.19. Because most directory versions were affected, we added workaround to make sure that we examined the contents of 503-replies to make sure there wasn't any data for them to find. But now that such routers are nonexistent, we can remove this code. (Even if somebody fired up an 0.1.2.19 directory cache today, it would still be fine to ignore data in its erroneous 503 replies.)
Diffstat (limited to 'changes')
-rw-r--r--changes/bug539_removal6
1 files changed, 6 insertions, 0 deletions
diff --git a/changes/bug539_removal b/changes/bug539_removal
new file mode 100644
index 0000000000..dbff43de18
--- /dev/null
+++ b/changes/bug539_removal
@@ -0,0 +1,6 @@
+ o Removed code
+ - Removed workaround code to handle directory responses from
+ servers that had bug 539 (they would send HTTP status 503
+ responses _and_ send a body too). Since only server versions
+ before 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer
+ reason to keep the workaround in place.