| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
This is part of rationalizing the structure of TorClient so we can
refactor startup logic, and so that RPC code can reason about object
identity. See #2469.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This option affects all socks listeners, because:
- We don't have a convenient way to associate an option with each
port.
- The main purpose of having this option is as a switch in case we
discover a major problem with this code.
|
| | |
|
| |
|
|
|
|
|
|
| |
This change lets us avoid spawning extra tasks (due to one-direction
nature of copy_interactive), and avoid some lock contention (due to
use of AsyncReadExt::split).
Addresses part of #786.
|
| |
|
|
|
|
|
| |
Apparently the http_connect refactoring made these no longer
trigger.
Closes #2226
|
| | |
|
| |
|
|
|
| |
This will let us speak HTTP CONNECT as well; there is a stub
for initiating an http proxy.
|
| |
|
|
| |
This will let us implement bilingual HTTP proxies.
|
| |
|
|
| |
This is _all_ renaming and comment adjustments.
|
|
|
We want to abstract every part of this code that knows that it's
speaking SOCKS, so that we can in turn add a new proxy type.
Note that several methods and types here have names that are no
longer appropriate for their functionality. I'll revise those in a
later commit.
|
