-
Notifications
You must be signed in to change notification settings - Fork 38
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
GitLab - 406 Not Acceptable download archive error #97
Comments
Gitlab Personal Access token is used, with proper scope(downloads properly using other HTTP clients) output for:
mentioned repo is private, in a group. |
Hey, I have the same problem, did you find any solutions ? @professorhaseeb |
DescriptionGood evening, guys! I have the same problem and I tried all possible solutions to the problem. This doesn't work. At the same time, everything works fine via curl and postman. Even the docker authorizes successfully, but the giget (and any node.js apps) cannot execute this request. I also got headers and cookies from successful requests - that doesn't work either. It seems to me that these may be features of the Gitlab settings. Do you have any ideas @tebaly @professorhaseeb @zola33dsf? I would be very grateful for your advice. Error with CI/CD
Success with CURL
P.S. By the way, if you have problems with CORS - nitro proxy works great. |
I have the same problem, with gitlab. Personal public repository.
P.S github repositories work without error under identical conditions
Maybe giget is not sending an additional header on request in the case of gitlab - https://stackoverflow.com/questions/14251851/what-is-406-not-acceptable-response-in-http |
After a deep and long research, I found these hotlinking rules on gitlab. In my fork giget downloading archive from gitlab works without errors. |
The issue should be fixed with workaround in #123 in latest version. (thanks @andreymart-test ❤️ ) |
Environment
Whith own registry, not working
Reproduction
Whith own registry, not working
Describe the bug
Whith own registry, not working
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: