diff options
author | Maximilian Hils <git@maximilianhils.com> | 2015-09-03 18:55:38 +0200 |
---|---|---|
committer | Maximilian Hils <git@maximilianhils.com> | 2015-09-03 18:55:38 +0200 |
commit | 14457f29b3d89e234d0791c4980e5cf9514185dd (patch) | |
tree | 9a12632fea816eb5a7f701d3e92670dc4009ccfe /libmproxy/protocol/tls.py | |
parent | 99126f62ed947847eba4cfa687cb0b0f012092bb (diff) | |
download | mitmproxy-14457f29b3d89e234d0791c4980e5cf9514185dd.tar.gz mitmproxy-14457f29b3d89e234d0791c4980e5cf9514185dd.tar.bz2 mitmproxy-14457f29b3d89e234d0791c4980e5cf9514185dd.zip |
docs++
Diffstat (limited to 'libmproxy/protocol/tls.py')
-rw-r--r-- | libmproxy/protocol/tls.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/libmproxy/protocol/tls.py b/libmproxy/protocol/tls.py index a62b1a22..88a8398f 100644 --- a/libmproxy/protocol/tls.py +++ b/libmproxy/protocol/tls.py @@ -237,8 +237,8 @@ class TlsLayer(Layer): If so, we first connect to the server and then to the client. If not, we only connect to the client and do the server_ssl lazily on a Connect message. - An additional complexity is that establish ssl with the server may require a SNI value from the client. - In an ideal world, we'd do the following: + An additional complexity is that establish ssl with the server may require a SNI value from + the client. In an ideal world, we'd do the following: 1. Start the SSL handshake with the client 2. Check if the client sends a SNI. 3. Pause the client handshake, establish SSL with the server. |