summaryrefslogtreecommitdiff
path: root/src/or/connection.c
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-08-24 17:09:56 -0400
committerNick Mathewson <nickm@torproject.org>2011-08-24 17:31:32 -0400
commit59d0f750c972011372febefbee958b37a17a0569 (patch)
treebb8da76fc73ba427afd23f54f7465a469cd3ba11 /src/or/connection.c
parentede9cd4f99e4cd1c0c4bcf1a3ac994e87054cc2d (diff)
downloadtor-59d0f750c972011372febefbee958b37a17a0569.tar.gz
tor-59d0f750c972011372febefbee958b37a17a0569.zip
Apply rate-limiting to the lowest bufferevent in the stack.
When we're doing filtering ssl bufferevents, we want the rate-limits to apply to the lowest level of the bufferevent stack, so that we're actually limiting bytes sent on the network. Otherwise, we'll read from the network aggressively, and only limit stuff as we process it.
Diffstat (limited to 'src/or/connection.c')
-rw-r--r--src/or/connection.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/or/connection.c b/src/or/connection.c
index f8f82a30dd..c4cbef4c9d 100644
--- a/src/or/connection.c
+++ b/src/or/connection.c
@@ -2509,7 +2509,7 @@ connection_enable_rate_limiting(connection_t *conn)
if (conn->bufev) {
if (!global_rate_limit)
connection_bucket_init();
- bufferevent_add_to_rate_limit_group(conn->bufev, global_rate_limit);
+ tor_add_bufferevent_to_rate_limit_group(conn->bufev, global_rate_limit);
}
}