On Wed, 9 Aug 2023, FC Stegerman wrote:
It seems that the unescaped dashes become U+2010. I was not expecting
that, hence my not realising what was going on. Sorry about that.
Thanks for this. I just filed this issue upstream:
https://github.com/curl/curl/issues/11635
With a pending
* Daniel Stenberg [2023-08-08 23:39]:
> On Tue, 8 Aug 2023, FC Stegerman wrote:
>
> > $ curl ‐‐connect‐timeout
> > curl: (6) Could not resolve host: xn--connecttimeout-462hah
> >
> > $ curl ‐‐connect‐timeout 2 -I example.com
> > curl: (6) Could not resolve host: xn--connecttimeout-462hah
>
>
On Tue, 8 Aug 2023, FC Stegerman wrote:
$ curl ‐‐connect‐timeout
curl: (6) Could not resolve host: xn--connecttimeout-462hah
$ curl ‐‐connect‐timeout 2 -I example.com
curl: (6) Could not resolve host: xn--connecttimeout-462hah
Those dashes in there are not ascii minuses, they are unicode e2
Package: curl
Version: 8.2.1-1
Severity: normal
X-Debbugs-Cc: f...@obfusk.net
Hi!
Something seems to be going wrong here:
$ curl ‐‐connect‐timeout
curl: (6) Could not resolve host: xn--connecttimeout-462hah
$ curl ‐‐connect‐timeout 2 -I example.com
curl: (6) Could not resolve host:
4 matches
Mail list logo
