Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] Archive of EGit update repos
Yes, thanks to the smartness of the webmaster this just works :-)

I compared the trace of downloading content.jar of the archived egit release 4.8 from archive.eclipse.org and download.eclipse.org 
and didn't find any suspicious difference except the redirect happening for the latter. It seems the client needs to support TLS 1.2 and
allow redirects.

Here is the verbose curl output for the download via redirect from https://download.eclipse.org/egit/updates-4.8/content.jar
I marked the relevant part of the difference for the redirect case in blue.

% 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 198.41.30.199:443...
* Connected to download.eclipse.org (198.41.30.199) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [109 bytes data]
* NPN, negotiated HTTP2 (h2)
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3250 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [589 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Next protocol (67):
} [36 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=CA; ST=Ontario; L=Ottawa; O=Eclipse.org Foundation, Inc.; OU=IT; CN=*.eclipse.org
* start date: Feb 3 00:00:00 2020 GMT
* expire date: Apr 4 12:00:00 2022 GMT
* subjectAltName: host "download.eclipse.org" matched cert's "*.eclipse.org"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x7fbcd6813600)
} [5 bytes data]
> GET /egit/updates-4.8/content.jar HTTP/2
> user-agent: curl/7.75.0
> accept: */*
>
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
} [5 bytes data]
< HTTP/2 301
< server: nginx
< date: Tue, 28 Sep 2021 09:52:03 GMT
< content-type: text/html
< content-length: 0
< x-nodeid: download1
< strict-transport-security: max-age=15552000; includeSubDomains; preload
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< x-xss-protection: 1; mode=block
< x-proxy-cache: MISS
<
{ [0 bytes data]
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
* Connection #0 to host download.eclipse.org left intact
* Issue another request to this URL: 'http://archive.eclipse.org/egit/updates-4.8/content.jar'
* Trying 198.41.30.199:80...
* Connected to archive.eclipse.org (198.41.30.199) port 80 (#1)
> GET /egit/updates-4.8/content.jar HTTP/1.1
> User-Agent: curl/7.75.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Server: nginx
< Date: Tue, 28 Sep 2021 09:52:03 GMT
< Content-Type: text/html
< Content-Length: 162
< Connection: keep-alive
<
* Ignoring the response-body
{ [162 bytes data]
100 162 100 162 0 0 194 0 --:--:-- --:--:-- --:--:-- 194
* Connection #1 to host archive.eclipse.org left intact
* Issue another request to this URL: 'https://archive.eclipse.org/egit/updates-4.8/content.jar'
* Trying 198.41.30.199:443...
* Connected to archive.eclipse.org (198.41.30.199) port 443 (#2)
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* ALPN, offering h2
* ALPN, offering http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [109 bytes data]
* NPN, negotiated HTTP2 (h2)
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [3250 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [589 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Next protocol (67):
} [36 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=CA; ST=Ontario; L=Ottawa; O=Eclipse.org Foundation, Inc.; OU=IT; CN=*.eclipse.org
* start date: Feb 3 00:00:00 2020 GMT
* expire date: Apr 4 12:00:00 2022 GMT
* subjectAltName: host "archive.eclipse.org" matched cert's "*.eclipse.org"
* issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
* SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x7fbcd6813600)
} [5 bytes data]
> GET /egit/updates-4.8/content.jar HTTP/2
> user-agent: curl/7.75.0
> accept: */*
>
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
} [5 bytes data]
< HTTP/2 200
< server: nginx
< date: Tue, 28 Sep 2021 09:52:04 GMT
< content-type: application/x-java-archive
< content-length: 25374
< last-modified: Tue, 13 Jun 2017 02:05:45 GMT
< etag: "631e-551cddf985040"
< accept-ranges: bytes
< x-nodeid: download2
< strict-transport-security: max-age=15552000; includeSubDomains; preload
< x-frame-options: SAMEORIGIN
< x-content-type-options: nosniff
< x-xss-protection: 1; mode=block
< x-proxy-cache: MISS
<
{ [16069 bytes data]
100 25374 100 25374 0 0 15203 0 0:00:01 0:00:01 --:--:-- 35738
* Connection #2 to host archive.eclipse.org left intact

On Tue, Sep 28, 2021 at 2:06 AM Kit Lo <kitlo@xxxxxxxxxx> wrote:

After more investigation, I found that Eclipse Foundation did re-direct all requests from download.eclipse.org to archive.eclipse.org automatically. However, I suspect that due to different SSL/TLS configurations between the two servers, I received the following message for Eclipse project R4_7_maintenance build:

[ERROR] Failed to resolve target definition /lts/git-eclipse/R4_7_maintenance/eclipse.platform.releng.prereqs.sdk/eclipse-sdk-prereqs.target: Failed to load p2 metadata repository from location http://download.eclipse.org/egit/updates-4.7: Unable to read repository at http://download.eclipse.org/egit/updates-4.7/content.xml.xz. Received fatal alert: handshake_failure

Searched the internet for clues. Tried to upgrade the Java on the build machine resolved the problem.

Sorry for the false alarm!

Regards,
Kit Lo
Eclipse Babel Project Lead
IBM Eclipse SDK (IES) Technical Lead and Release Manager

"Matthias Sohn" <matthias.sohn@xxxxxxxxx> wrote on 09/24/2021 08:55:14 AM:

> From: "Matthias Sohn" <matthias.sohn@xxxxxxxxx>
> To: "Kit Lo" <kitlo@xxxxxxxxxx>
> Cc: "EGit developer discussion" <egit-dev@xxxxxxxxxxx>
> Date: 09/24/2021 08:55 AM
> Subject: Re: [egit-dev] Archive of EGit update repos
>
> On Fri, Sep 24, 2021 at 8:15 AM Kit Lo <kitlo@xxxxxxxxxx> wrote:
> I just noticed that EGit 4.* to 5.8 update repos have been archived from
> download.eclipse.org to archive.eclipse.org. I did not hear any
> announcement about the plan for the archive. Was that intentional?
> Eclipse project depends on EGit. The archive is breaking all Eclipse
> builds for R4_17_maintenance and older. Is there any chance of
> restoring the EGit 4.* to 5.8 update repos to download.eclipse.org?

> Sorry, I didn't intend to cause trouble.
> I did that since the webmaster asked all projects (I think on the
> cross-projects list)
> to free space on the download server and didn't expect anyone to
> still depend on these old versions.
>
> Is there some way we can link from download.eclipse.org to the
> archived p2 repos on archive.eclipse.org ?
>
> -Matthias 
>
> Regards,
> Kit Lo
> Eclipse Babel Project Lead
> IBM Eclipse SDK (IES) Technical Lead and Release Manager

> _______________________________________________
> egit-dev mailing list
> egit-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/
> mailman/listinfo/egit-dev

_______________________________________________
egit-dev mailing list
egit-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/egit-dev

Back to the top