Re: Bug in curl_easy_reset: Re-using the handle fails with HTTP 401

On Wed, 17 Jan 2018, Ruurd Beerstra via curl-library wrote: When the code is executed to establish a session to host 1, do a curl_easy_reset, then contact host 2 (re-using the handle), the result is a HTTP 401 (unauthorized) for the connection to host 2. Hi again! Was the test program suppos

Re: Certificate update question

[Resend to list] On Mon, Jan 22, 2018 at 12:37 PM, Dave S wrote: > On Sat, Jan 20, 2018 at 2:49 AM, Daniel Stenberg wrote: > On Thu, 21 Dec 2017, Dave S via curl-library wrote: >> >> (Sorry for not having responded sooner.) >> >> The certificates for TBD Portal (tbd.tbdservice.com) and MainTBD

Re: IPv6 address treated as a DNS name when compiled w/o IPV6 support

On Mon, 22 Jan 2018, John Hascall via curl-library wrote: ​I would like to suggest that returning some sort of error like CURLE_NO_IPV6_SUPPORT (or at least CURLE_NOT_BUILT_IN ​) ​would be more helpful. Hi again, I've submitted my first take on a fix here: https://github.com/curl/curl/pul

Re: IPv6 address treated as a DNS name when compiled w/o IPV6 support

On Mon, 22 Jan 2018, John Hascall via curl-library wrote: ​I would like to suggest that returning some sort of error like CURLE_NO_IPV6_SUPPORT (or at least CURLE_NOT_BUILT_IN ​) ​would be more helpful. Thanks for your report. This is clearly an oversight on our behalf. Together with a helpf

IPv6 address treated as a DNS name when compiled w/o IPV6 support

[From My Stackoverflow question ] I am attempting to use curl's CURLOPT_CONNECT_TO option to connect to a specific address (rather than the result of the DNS