Availability of flyway-core-4.0.3.jar keeps changing

The availability of the below jar from plugins.gradle keeps changing. Sometimes I get a 404 and sometimes the jar is available.


Experiencing similar issues:

bash-4.3# curl -D out.txt -H 'Pragma: akamai-x-cache-on, akamai-x-cache-remote-on, akamai-x-check-cacheable, akamai-x-get-cache-key, akamai-x-get-ssl-client-session-id, akamai-x-get-true-cache-key, akamai-x-get-request-id' -sL https://jcenter.bintray.com/org/springframework/boot/spring-boot-tools/1.5.3.RELEASE/spring-boot-tools-1.5.3.RELEASE.pom
The requested path was not found.bash-4.3# cat out.txt
HTTP/1.1 404 Not Found
Server: nginx
Date: Wed, 28 Mar 2018 20:30:16 GMT
Content-Type: text/plain
Transfer-Encoding: chunked
Connection: keep-alive

These artifacts are hosted by Bintray and redirected to there from the plugin portal.

curl -v https://plugins.gradle.org/m2/org/flywaydb/flyway-core/4.0.3/flyway-core-4.0.3.jar
*   Trying
* Connected to plugins.gradle.org ( port 443 (#0)
*  SSL certificate verify ok.
> GET /m2/org/flywaydb/flyway-core/4.0.3/flyway-core-4.0.3.jar HTTP/1.1
> Host: plugins.gradle.org
> User-Agent: curl/7.54.0
> Accept: */*
< HTTP/1.1 303 See Other
< Date: Wed, 28 Mar 2018 20:54:14 GMT
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: __cfduid=de00d17a341dc997edc2edd4cc89e9eda1522270454; expires=Thu, 28-Mar-19 20:54:14 GMT; path=/; domain=.gradle.org; HttpOnly
< Location: https://jcenter.bintray.com/org/flywaydb/flyway-core/4.0.3/flyway-core-4.0.3.jar
< Via: 1.1 vegur
< CF-Cache-Status: MISS
< Expires: Thu, 29 Mar 2018 08:54:14 GMT
< Cache-Control: public, max-age=43200
< Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< Server: cloudflare
< CF-RAY: 402cfda2ab1439ca-PHX
* Connection #0 to host plugins.gradle.org left intact

This seems to be related to Bintray’s ongoing CDN issues. See http://status.bintray.com/ and please report this to their support team.

1 Like

Yep, reported. We flipped our repo from Bintray to MavenCentral and everything is working smoothly again for us. Thanks for the help.