-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve() fails on HEAD request returning 403 forbidden #390
Comments
amalcgcg
changed the title
Resolve() fails on HEAD request returning 403 forbidde
Resolve() fails on HEAD request returning 403 forbidden
Apr 14, 2020
I attempted a fix in #387 The test suite passes on my local system, but for some reason the CI builds are failing. Could you please advise? |
Thanks -- I'm going to take a closer look at this today. |
kevinushey
added a commit
that referenced
this issue
Apr 17, 2020
I verified that this is fixed by da7bffd. Thanks! |
Great; I'm glad to hear it! |
Interestingly, looks like GitHub now allows these sorts of HEAD requests:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When retrieving a package using Source == URL, some packages will fail with "Error: download failed [file was truncated]." The root cause is a 403 forbidden returned by the initial HEAD request to get the file size. This in turn happens because some sites, including GitHub's service on AWS, don't allow HEAD requests.
See this same issue in a different software tool at cavaliergopher/grab#43
renv.lock contents to reproduce:
The text was updated successfully, but these errors were encountered: