Replies: 5 comments 6 replies
-
Backtrace if it helps
|
Beta Was this translation helpful? Give feedback.
-
I would reach out to the provider of your private gem server and see if they are appending -gzip to the etag, which bundler is not expecting |
Beta Was this translation helpful? Give feedback.
-
Hi so I reached out to them and indeed they are appending it... however... In
This header led to my problems, removing it results in the correct behavior...maybe such a header should be overridden for this request? If this is an acceptable change I'd like to submit a PR ... would be cool to contribute 😁 |
Beta Was this translation helpful? Give feedback.
-
For me, this was resolved by updating bundler from 2.1.4 to 2.3.7. |
Beta Was this translation helpful? Give feedback.
-
Closing since it was reported as resolved. |
Beta Was this translation helpful? Give feedback.
-
Hi I'm using an internal setup(Sonatype Nexus they just pushed support for /info) and I keep running into the following for a private gem:
Where VALUE is the checksum string.
I tried digging into the bundler code but could not find anything myself, my question is do you think bundler is adding that trailing
-gzip
?The ETag when I curl the url that is hit by bundler manually is
VALUE
without the-gzip
so I am confused as to where it is coming from ... I got the URL from running bundler with verbose flag.I already tried nuking
~/.bundler/cache
for what it is worth.I am using
Appreciate the help.
Beta Was this translation helpful? Give feedback.
All reactions