Skip to content
This repository has been archived by the owner on Oct 14, 2021. It is now read-only.

Multiple binaries match request: openjdk 8 ea artefacts #187

Closed
jerboaa opened this issue Apr 30, 2020 · 1 comment · Fixed by #188
Closed

Multiple binaries match request: openjdk 8 ea artefacts #187

jerboaa opened this issue Apr 30, 2020 · 1 comment · Fixed by #188
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jerboaa
Copy link
Contributor

jerboaa commented Apr 30, 2020

$ curl -v https://api.adoptopenjdk.net/v3/binary/latest/8/ea/linux/x64/jdk/hotspot/normal/openjdk
*   Trying 104.17.158.60:443...
* TCP_NODELAY set
* Connected to api.adoptopenjdk.net (104.17.158.60) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* 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-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=CA; L=San Francisco; O=Cloudflare, Inc.; CN=adoptopenjdk.net
*  start date: Mar 19 00:00:00 2020 GMT
*  expire date: Oct  9 12:00:00 2020 GMT
*  subjectAltName: host "api.adoptopenjdk.net" matched cert's "*.adoptopenjdk.net"
*  issuer: C=US; ST=CA; L=San Francisco; O=CloudFlare, Inc.; CN=CloudFlare Inc ECC CA-2
*  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
* Using Stream ID: 1 (easy handle 0x55fde2e77a00)
> GET /v3/binary/latest/8/ea/linux/x64/jdk/hotspot/normal/openjdk HTTP/2
> Host: api.adoptopenjdk.net
> User-Agent: curl/7.65.3
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS == 256)!
< HTTP/2 400 
< date: Thu, 30 Apr 2020 10:00:17 GMT
< content-type: application/octet-stream
< content-length: 192
< set-cookie: __cfduid=def3580af804e6c93e66e4dcfa653fa051588240817; expires=Sat, 30-May-20 10:00:17 GMT; path=/; domain=.adoptopenjdk.net; HttpOnly; SameSite=Lax
< access-control-allow-origin: *
< set-cookie: b7b892882bae631693e1ea44963ef628=262a5780929c0750267ffcad1ee2cf91; path=/; HttpOnly; Secure
< cf-cache-status: DYNAMIC
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< server: cloudflare
< cf-ray: 58c06a346ed9cbc4-VIE
< alt-svc: h3-27=":443"; ma=86400, h3-25=":443"; ma=86400, h3-24=":443"; ma=86400, h3-23=":443"; ma=86400
< cf-request-id: 026c20b4bf0000cbc4af30f200000001
< 
* Connection #0 to host api.adoptopenjdk.net left intact
{"errorMessage":"Multiple binaries match request: [OpenJDK8U-jdk-jfr_x64_linux_8u262b01_ea.tar.gz, OpenJDK8U-jdk_x64_linux_8u262b01_ea.tar.gz, OpenJDK8U-jre-jfr_x64_linux_8u262b01_ea.tar.gz]"}

With the latest EA release of 8u262-b01, which now includes JFR enabled and JFR disabled (default) builds, the API gets confused. Can we ignore jdk-jfr and jre-jfr matching binaries?

@jerboaa
Copy link
Contributor Author

jerboaa commented Apr 30, 2020

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants