diff options
| author | Daniel Stenberg <daniel@haxx.se> | 2007-02-27 22:12:15 +0000 |
|---|---|---|
| committer | Daniel Stenberg <daniel@haxx.se> | 2007-02-27 22:12:15 +0000 |
| commit | 060f7ca2d2a7f5c8845a62a143c1d9fa988d1269 (patch) | |
| tree | ece6bd391dfb56c808fae61e599e508baa83fd7a /CHANGES | |
| parent | 638c715a5122697a34685615f24855b8417562f1 (diff) | |
- Hang Kin Lau found and fixed: When I use libcurl to connect to an https
server through a proxy and have the remote https server port set using the
CURLOPT_PORT option, protocol gets reset to http from https after the first
request.
User defined URL was modified internally by libcurl and subsequent reuse of
the easy handle may lead to connection using a different protocol (if not
originally http).
I found that libcurl hardcoded the protocol to "http" when it tries to
regenerate the URL if CURLOPT_PORT is set. I tried to fix the problem as
follows and it's working fine so far
Diffstat (limited to 'CHANGES')
| -rw-r--r-- | CHANGES | 14 |
1 files changed, 14 insertions, 0 deletions
@@ -6,6 +6,20 @@ Changelog +Daniel (27 February 2007) +- Hang Kin Lau found and fixed: When I use libcurl to connect to an https + server through a proxy and have the remote https server port set using the + CURLOPT_PORT option, protocol gets reset to http from https after the first + request. + + User defined URL was modified internally by libcurl and subsequent reuse of + the easy handle may lead to connection using a different protocol (if not + originally http). + + I found that libcurl hardcoded the protocol to "http" when it tries to + regenerate the URL if CURLOPT_PORT is set. I tried to fix the problem as + follows and it's working fine so far + Daniel (25 February 2007) - Adam D. Moss made the HTTP CONNECT procedure less blocking when used from the multi interface. Note that it still does a part of the connection in a |