netshade
(Chris Zelenak)
May 7, 2024, 4:14pm
1
For the extremely old 1.7.3 release, the download link https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.7.3.zip now returns a 403. This breaks any workflows that depend on testing on older ES versions.
Reported here because it is not obvious how else to report technical issues w/ the ES website.
What's the exact error? This link works for me:
$ curl --http1.1 -vvv https://download.elastic.co/elasticsearch/elasticsearch/elasticsearch-1.7.3.zip | shasum
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 34.120.127.130:443...
* Connected to download.elastic.co (34.120.127.130) port 443
* ALPN: curl offers http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [321 bytes data]
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [21 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [4089 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN: server accepted http/1.1
* Server certificate:
* subject: CN=elastic.co
* start date: May 2 17:52:51 2024 GMT
* expire date: Jul 31 17:52:50 2024 GMT
* subjectAltName: host "download.elastic.co" matched cert's "download.elastic.co"
* issuer: C=US; O=Let's Encrypt; CN=R3
* SSL certificate verify ok.
* using HTTP/1.1
> GET /elasticsearch/elasticsearch/elasticsearch-1.7.3.zip HTTP/1.1
> Host: download.elastic.co
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Accept-Ranges: bytes
< Strict-Transport-Security: max-age=31536000; includeSubDomains
< Via: 1.1 google
< Date: Tue, 07 May 2024 19:07:49 GMT
< Cache-Control: public, max-age=600
< Last-Modified: Wed, 16 May 2018 02:38:35 GMT
< ETag: "4a213d18de1bee63d2a2b01eb3f579d1-4"
< Content-Type: binary/octet-stream
< Content-Length: 31795251
< Age: 51
< Alt-Svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
<
{ [966 bytes data]
100 30.3M 100 30.3M 0 0 3818k 0 0:00:08 0:00:08 --:--:-- 3826k
* Connection #0 to host download.elastic.co left intact
5eadfac73bb90a6dd07b0658fc982035e62945eb -
netshade
(Chris Zelenak)
May 11, 2024, 11:21am
3
I no longer am receiving the error - the best I could tell you was that it was an HTTP 403 at the time. Whatever was happening now appears to have resolved.
1 Like