diff options
| author | Roger Dingledine <arma@torproject.org> | 2016-10-02 19:13:35 -0400 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2016-10-02 19:13:35 -0400 |
| commit | 9228db5f1bee0b715b73ba6f8c11f5eb77d59f62 (patch) | |
| tree | e1ad879452578e5c4143dbf45eaf3241fa204d7d | |
| parent | 53255e925c474f9d5cb30c1de4da025e6d709e9a (diff) | |
| download | tor-9228db5f1bee0b715b73ba6f8c11f5eb77d59f62.tar.gz tor-9228db5f1bee0b715b73ba6f8c11f5eb77d59f62.zip | |
remove confusing comment about conditional consensus download
We removed that feature in 0.2.4.2-alpha, but some comments seem to
have lingered.
I didn't add a changes/ file since this is just internal code cleanup.
| -rw-r--r-- | src/or/directory.c | 9 |
1 files changed, 3 insertions, 6 deletions
diff --git a/src/or/directory.c b/src/or/directory.c index 52b14b9bae..1f894d9fb3 100644 --- a/src/or/directory.c +++ b/src/or/directory.c @@ -495,9 +495,6 @@ MOCK_IMPL(void, directory_get_from_dirserver, ( * sort of dir fetch we'll be doing, so it won't return a bridge * that can't answer our question. */ - /* XXX+++++ Not all bridges handle conditional consensus downloading, - * so, for now, never assume the server supports that. -PP - * Is that assumption still so in 2016? -NM */ const node_t *node = choose_random_dirguard(type); if (node && node->ri) { /* every bridge has a routerinfo. */ @@ -1305,9 +1302,9 @@ compare_strs_(const void **a, const void **b) /** Return the URL we should use for a consensus download. * - * This url depends on whether or not the server we go to - * is sufficiently new to support conditional consensus downloading, - * i.e. GET .../consensus/<b>fpr</b>+<b>fpr</b>+<b>fpr</b> + * Use the "conditional consensus downloading" feature described in + * dir-spec.txt, i.e. + * GET .../consensus/<b>fpr</b>+<b>fpr</b>+<b>fpr</b> * * If 'resource' is provided, it is the name of a consensus flavor to request. */ |