Cargo download dependency failed

yuyang-ok · May 23, 2023, 11:02am

yuyang@yuyangdeMacBook-Pro deno % cargo version 
cargo 1.68.2 (6feb7c9cf 2023-03-26)

yuyang@yuyangdeMacBook-Pro deno % cargo t -v

**error****:** failed to download from `https://crates.io/api/v1/crates/zstd-sys/2.0.7+zstd.1.5.4/download`

Caused by:

[2] Failed initialization ([CONN-1-0] send: no filter connected)

yuyang@yuyangdeMacBook-Pro deno %

The url is accessable from my local machine.

yuyang@yuyangdeMacBook-Pro Downloads % wget https://crates.io/api/v1/crates/zstd-sys/2.0.7+zstd.1.5.4/download 
--2023-05-23 19:03:27--  https://crates.io/api/v1/crates/zstd-sys/2.0.7+zstd.1.5.4/download
Resolving crates.io (crates.io)... 2600:9000:2251:c000:c:7ed3:240:93a1, 2600:9000:2251:400:c:7ed3:240:93a1, 2600:9000:2251:e00:c:7ed3:240:93a1, ...
Connecting to crates.io (crates.io)|2600:9000:2251:c000:c:7ed3:240:93a1|:443... connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://static.crates.io/crates/zstd-sys/zstd-sys-2.0.7+zstd.1.5.4.crate [following]
--2023-05-23 19:03:28--  https://static.crates.io/crates/zstd-sys/zstd-sys-2.0.7+zstd.1.5.4.crate
Resolving static.crates.io (static.crates.io)... 2600:9000:2490:9000:1b:d7a6:ee00:93a1, 2600:9000:2490:a00:1b:d7a6:ee00:93a1, 2600:9000:2490:b400:1b:d7a6:ee00:93a1, ...
Connecting to static.crates.io (static.crates.io)|2600:9000:2490:9000:1b:d7a6:ee00:93a1|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 732100 (715K) [application/gzip]
Saving to: ‘download’

download                      100%[=================================================>] 714.94K   391KB/s    in 1.8s    

2023-05-23 19:03:31 (391 KB/s) - ‘download’ saved [732100/732100]

yuyang@yuyangdeMacBook-Pro Downloads %

kornel · May 23, 2023, 12:04pm

This error message looks unusual. Do you have any 3rd party firewall or antivirus installed? It suggests something wanted to intercept network connections and did it badly.

Cargo uses libcurl to download things.

If you have a firewall, it could be applied to each process differently and allowing wget, but blocking cargo.

yuyang-ok · May 23, 2023, 10:47pm

I disable the firewall the problem continues.

yuyang@yuyangdeMacBook-Pro deno % curl -v https://crates.io/api/v1/crates/zstd-sys/2.0.7+zstd.1.5.4/download

* Trying 13.32.99.58:443...

* Trying [2600:9000:2251:ce00:c:7ed3:240:93a1]:443...

* Connected to crates.io (13.32.99.58) port 443 (#0)

* ALPN: offers h2,http/1.1

* (304) (OUT), TLS handshake, Client hello (1):

* CAfile: /etc/ssl/cert.pem

* CApath: none

* (304) (IN), TLS handshake, Server hello (2):

* (304) (IN), TLS handshake, Unknown (8):

* (304) (IN), TLS handshake, Certificate (11):

* (304) (IN), TLS handshake, CERT verify (15):

* (304) (IN), TLS handshake, Finished (20):

* (304) (OUT), TLS handshake, Finished (20):

* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256

* ALPN: server accepted h2

* Server certificate:

* subject: CN=crates.io

* start date: Jan 25 00:00:00 2023 GMT

* expire date: Feb 23 23:59:59 2024 GMT

* subjectAltName: host "crates.io" matched cert's "crates.io"

* issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M02

* SSL certificate verify ok.

* using HTTP/2

* h2h3 [:method: GET]

* h2h3 [:path: /api/v1/crates/zstd-sys/2.0.7+zstd.1.5.4/download]

* h2h3 [:scheme: https]

* h2h3 [:authority: crates.io]

* h2h3 [user-agent: curl/7.88.1]

* h2h3 [accept: */*]

* Using Stream ID: 1 (easy handle 0x7f8300010a00)

> GET /api/v1/crates/zstd-sys/2.0.7+zstd.1.5.4/download HTTP/2

> Host: crates.io

> user-agent: curl/7.88.1

> accept: */*

>

< HTTP/2 302

< content-length: 0

< location: https://static.crates.io/crates/zstd-sys/zstd-sys-2.0.7+zstd.1.5.4.crate

< server: nginx

< date: Tue, 23 May 2023 22:46:40 GMT

< x-content-type-options: nosniff

< x-frame-options: SAMEORIGIN

< x-xss-protection: 0

< content-security-policy: default-src 'self'; connect-src 'self' *.ingest.sentry.io https://docs.rs https://play.rust-lang.org https://static.crates.io; script-src 'self' 'unsafe-eval' 'sha256-n1+BB7Ckjcal1Pr7QNBh/dKRTtBQsIytFodRiIosXdE='; style-src 'self' 'unsafe-inline' https://code.cdn.mozilla.net; font-src https://code.cdn.mozilla.net; img-src *; object-src 'none'

< access-control-allow-origin: *

< strict-transport-security: max-age=31536000; includeSubDomains

< via: 1.1 vegur, 1.1 cb605905cea2427f1d9f13acc778e822.cloudfront.net (CloudFront)

< vary: Accept,Accept-Encoding,Cookie

< x-cache: Miss from cloudfront

< x-amz-cf-pop: FRA60-P3

< x-amz-cf-id: l-j_cHrBQil7qm7v9pWWfJ99rHzGdRgMhJnQ5h-OoaxJMSfglQ63ng==

<

* Connection #0 to host crates.io left intact

yuyang-ok · May 23, 2023, 11:02pm

github.com

curl/curl/blob/master/docs/CONNECTION-FILTERS.md

# curl connection filters

Connection filters is a design in the internals of curl, not visible in its public API. They were added 
in curl v7.xx.x. This document describes the concepts, its high level implementation and the motivations.

## Filters

A "connection filter" is a piece of code that is responsible for handling a range of operations
of curl's connections: reading, writing, waiting on external events, connecting and closing down - to name the most important ones.

The most important feat of connection filters is that they can be stacked on top of each other (or "chained" if you prefer that metaphor). In the common scenario that you want to retrieve a `https:` url with curl, you need 2 basic things to send the request and get the response: a TCP connection, represented by a `socket` and a SSL instance en- and decrypt over that socket. You write your request to the SSL instance, which encrypts and writes that data to the socket, which then sends the bytes over the network.

With connection filters, curl's internal setup will look something like this (cf for connection filter):

```
Curl_easy *data         connectdata *conn        cf-ssl        cf-socket
+----------------+      +-----------------+      +-------+     +--------+
|https://curl.se/|----> | properties      |----> | keys  |---> | socket |--> OS --> network
+----------------+      +-----------------+      +-------+     +--------+

This file has been truncated. show original

sunjiang · June 8, 2023, 4:00pm

l also meet this problem. has solution now?

yuyang-ok · June 8, 2023, 11:44pm

Yeah.

check this out .

sunjiang · June 9, 2023, 2:37am

thanks

system · September 7, 2023, 2:37am

This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.