aboutsummaryrefslogtreecommitdiff
path: root/spec/address-spec.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/address-spec.md')
-rw-r--r--spec/address-spec.md7
1 files changed, 5 insertions, 2 deletions
diff --git a/spec/address-spec.md b/spec/address-spec.md
index 272e366..0254e24 100644
--- a/spec/address-spec.md
+++ b/spec/address-spec.md
@@ -11,10 +11,11 @@ Table of Contents
```
<a id="address-spec.txt-1"></a>
+
# Overview
Most of the time, Tor treats user-specified hostnames as opaque: When
-the user connects to www.torproject.org, Tor picks an exit node and uses
+the user connects to <www.torproject.org>, Tor picks an exit node and uses
that node to connect to "www.torproject.org". Some hostnames, however,
can be used to override Tor's default behavior and circuit-building
rules.
@@ -26,6 +27,7 @@ substituted for certain IP addresses using the MapAddress configuration
option or the MAPADDRESS control command.
<a id="address-spec.txt-2"></a>
+
# .exit
```text
@@ -61,6 +63,7 @@ to potential application-level attacks.
```
<a id="address-spec.txt-3"></a>
+
# .onion
```text
@@ -93,6 +96,7 @@ The "ignored" portion of the address is intended for use in vhosting, and
is supported in Tor 0.2.4.10-alpha and later.
<a id="address-spec.txt-4"></a>
+
# .noconnect
SYNTAX: [string].noconnect
@@ -105,4 +109,3 @@ using the same instance of Tor that they're controlling.
This feature was added in Tor 0.1.2.4-alpha, and taken out in Tor
0.2.2.1-alpha over fears that it provided another avenue for detecting
Tor users via application-level web tricks.
-