diff options
| author | Viktor Szakats <vszakats@users.noreply.github.com> | 2018-02-23 23:29:01 +0000 |
|---|---|---|
| committer | Viktor Szakats <vszakats@users.noreply.github.com> | 2018-02-23 23:29:01 +0000 |
| commit | 7e35eb77292fe6464889ddc8329c6a64136f969d (patch) | |
| tree | 76b1bdd02473d44be6773d0c61bbe8e98aeb8ffd /docs/libcurl/libcurl-tutorial.3 | |
| parent | 06df42410e8829b70812b56664ab9fe3c77b683a (diff) | |
spelling fixes
Detected using the `codespell` tool.
Also contains one URL protocol upgrade.
Closes https://github.com/curl/curl/pull/2334
Diffstat (limited to 'docs/libcurl/libcurl-tutorial.3')
| -rw-r--r-- | docs/libcurl/libcurl-tutorial.3 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/libcurl/libcurl-tutorial.3 b/docs/libcurl/libcurl-tutorial.3 index ab2cbeb99..741e08e4b 100644 --- a/docs/libcurl/libcurl-tutorial.3 +++ b/docs/libcurl/libcurl-tutorial.3 @@ -856,7 +856,7 @@ discussed. Instead, the only way to have SSL work over a HTTP proxy is to ask the proxy to tunnel trough everything without being able to check or fiddle with the traffic. -Opening an SSL connection over a HTTP proxy is therefor a matter of asking the +Opening an SSL connection over a HTTP proxy is therefore a matter of asking the proxy for a straight connection to the target host on a specified port. This is made with the HTTP request CONNECT. ("please mr proxy, connect me to that remote host"). |