[RTFACT-16517] Gem artifacts with dependency queries too long can’t be resolved from virtual repositories Created: 25/Apr/18 Updated: 13/Aug/19 Resolved: 16/Jul/19
|Project:||Artifactory Binary Repository|
|Affects Version/s:||5.10.3, 5.8.9|
|Fix Version/s:||6.12.0, 6.11.3|
|Reporter:||Angello Maggio||Assignee:||Omri Ziv|
|Sprint:||Pom - Sprint 1|
Certain Artifacts can't be resolved from a gems virtual repository due to their dependencies creating too long of a query parameter list.
This affect Gem versions > 2.1
One example is package aws-sdk. Note how the GET request has an incredibly long query parameter list.
Works with remote, and seems the 502 is not handled well on virtual:
Debug loggers don't give extra information, it could be something related to that 502 error, as that's the big difference in the outputs.
The long URL through cURL or Browser gives out the following for remote repository requests:
<h1>Error 502 Bad Gateway</h1>
<p>Details: cache-sjc3633-SJC 1525229284 1719933408</p>
<p>Varnish cache server</p>
For Virtual repositories, it simply returns a close bracket symbol " ] ".
|Comment by Aspect Capital [ 05/Sep/18 ]|
We've just noticed the same bug with Artifactory 5.10.4, it makes installing things like the AWS SDK impossible without temporarily pointing to a remote repository instead of a virtual one.
|Comment by Tim Perkins [ 14/May/19 ]|
Artifactory's Ruby gem support is close to unusable with this bug. This looks like a really interesting alternative: https://github.com/features/package-registry
|Comment by John Mellor [ 28/May/19 ]|
This critical bug is now over a year old. What is the fix status?