aboutsummaryrefslogtreecommitdiff
path: root/src/or/connection_edge.c
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2016-11-14 09:16:57 -0500
committerNick Mathewson <nickm@torproject.org>2016-11-14 09:16:57 -0500
commit307d244640ff9ad829bfe0769ddb2f903ec80ea8 (patch)
tree0c6271f123c0ac58a90e079c16c420cd9403edb0 /src/or/connection_edge.c
parent7918e219d45f2cac62b7c3d79fb1d4df4c5d65be (diff)
downloadtor-307d244640ff9ad829bfe0769ddb2f903ec80ea8.tar.gz
tor-307d244640ff9ad829bfe0769ddb2f903ec80ea8.zip
Fix a "shouldn't have reached this" warning in connection_edge.c
This was bug 20630; bugfix on f3e158ed where I thought I was committing a documentation-only fix but instead messed up the control flow too.
Diffstat (limited to 'src/or/connection_edge.c')
-rw-r--r--src/or/connection_edge.c8
1 files changed, 3 insertions, 5 deletions
diff --git a/src/or/connection_edge.c b/src/or/connection_edge.c
index 875c911f01..3874d52c23 100644
--- a/src/or/connection_edge.c
+++ b/src/or/connection_edge.c
@@ -1627,11 +1627,9 @@ connection_ap_handshake_rewrite_and_attach(entry_connection_t *conn,
}
tor_assert(!automap);
rep_hist_note_used_resolve(now); /* help predict this next time */
- }
+ } else if (socks->command == SOCKS_COMMAND_CONNECT) {
+ /* Now see if this is a connect request that we can reject immediately */
- /* Now see if this is a connect request that we can reject immediately */
- if (socks->command == SOCKS_COMMAND_CONNECT) {
- /* Special handling for attempts to connect */
tor_assert(!automap);
/* Don't allow connections to port 0. */
if (socks->port == 0) {
@@ -1771,7 +1769,7 @@ connection_ap_handshake_rewrite_and_attach(entry_connection_t *conn,
rep_hist_note_used_resolve(now); /* help predict this next time */
/* no extra processing needed */
} else {
- /* We should only be doing CONNECT or RESOLVE! */
+ /* We should only be doing CONNECT, RESOLVE, or RESOLVE_PTR! */
tor_fragile_assert();
}