Server returns code 400

Summary

Since a while now we see error 400 reported for some content a recent example is:

Caused by: java.io.IOException: Server returned HTTP code: 400 for URL https://download.eclipse.org/releases/ganymede/content.jar
    at org.eclipse.tycho.p2maven.transport.Headers.checkResponseCode (Headers.java:54)
    at org.eclipse.tycho.p2maven.transport.SharedHttpCacheStorage$CacheLine.lambda$fetchFile$0 (SharedHttpCacheStorage.java:282)
    at org.eclipse.tycho.p2maven.transport.Java11HttpTransportFactory$Java11HttpTransport.performGet (Java11HttpTransportFactory.java:166)
    at org.eclipse.tycho.p2maven.transport.Java11HttpTransportFactory$Java11HttpTransport.get (Java11HttpTransportFactory.java:113)
    at org.eclipse.tycho.p2maven.transport.SharedHttpCacheStorage$CacheLine.fetchFile (SharedHttpCacheStorage.java:243)
    at org.eclipse.tycho.p2maven.transport.SharedHttpCacheStorage$2.getCacheFile (SharedHttpCacheStorage.java:126)
    at org.eclipse.tycho.p2maven.transport.HttpTransportProtocolHandler.getFile (HttpTransportProtocolHandler.java:51)
    at org.eclipse.tycho.p2maven.transport.TychoRepositoryTransportCacheManager.createCache (TychoRepositoryTransportCacheManager.java:46)
    at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.getLocalFile (SimpleMetadataRepositoryFactory.java:73)
    at org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load (SimpleMetadataRepositoryFactory.java:93)
    at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad (MetadataRepositoryManager.java:65)
    at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository (AbstractRepositoryManager.java:849)
    at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository (AbstractRepositoryManager.java:739)
    at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository (MetadataRepositoryManager.java:107)

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low (but waste resources for rerun a job)

Impact

Builds fails and given we use a library at Tycho that works flawless for a large amount of HTTP request an error code of 400 (invalid request) seems highly unlikley.

In any case, if it even is a really invalid client request, we need to know what exactly make it invalid here. As the issue only occurs sporadically logging on the client side or debuging without the server log is impossible.