3 ms·
Not working for me?
by miniBill 3y ago
Not working for me?
- bookofjoe 3y agoTry this: https://www.wsj.com/tech/personal-tech/coffee-making-myths-that-might-be-holding-you-back-e16ea91c?st=egs7puu8vhb0jng&reflink=desktopwebshare_permalink https://www.wsj.com/tech/personal-tech/coffee-making-myths-t...
- forbiddenlake 3y agoIf you are getting a fake cloud flare captcha, then stop using cloudflare DNS (or any DNS that does not send ECS).
- miniBill 3y agoNo I'm just... not getting anything at all. $ curl -vv -sSL https://archive.ph/TO9Rr * Trying 89.253.237.26:443... * Connected to archive.ph (89.253.237.26) port 443 * ALPN: curl offers h2,http/1.1 * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384 * ALPN: server accepted h2 * Server certificate: * subject: CN=archive.ph * start date: Feb 4 02:37:14 2024 GMT * expire date: May 4 02:37:13 2024 GMT * subjectAltName: host "archive.ph" matched cert's "archive.ph" * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok. * using HTTP/2 * [HTTP/2] [1] OPENED stream for https://archive.ph/TO9Rr * [HTTP/2] [1] [:method: GET] * [HTTP/2] [1] [:scheme: https] * [HTTP/2] [1] [:authority: archive.ph] * [HTTP/2] [1] [:path: /TO9Rr] * [HTTP/2] [1] [user-agent: curl/8.4.0] * [HTTP/2] [1] [accept: */*] > GET /TO9Rr HTTP/2 > Host: archive.ph > User-Agent: curl/8.4.0 > Accept: */* > And then it just hangs forever