-
Notifications
You must be signed in to change notification settings - Fork 82
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
Proxying private repository doesn`t work #29
Comments
Well, it's certainly interesting: That seems to indicate there is no payload in the response. I would set a breakpoint in there at that line and examine the response object to see what you are getting from the remote. My guess is a 403 or something akin. NOTE: if you run Nexus Repo with the flag Not sure how handy you are with Java, etc... but figured I'd pop some info in on how to debug this and get a bit more info. |
did u create a private repo using satis? if that so then u have to parse include.json and transform it into /package/list.json for list all your projects, and a /p/%package%.json for a single one. `location =/packages/list.json { location ~ /p/ { `<?php header('Content-Type: application/json'); and since satis use tar instead of zip for package, u have to add tarball parser to nexus-composer |
What are you trying to do?
I am trying to proxy the private repo https://updates.ez.no/ttl
https://updates.ez.no/ttl/packages.json
What feature or behavior is this required for?
proxy a private composer repo
How could we solve this issue? (Not knowing is okay!)
Do not know.
Anything else?
Yes .. Packagist works for me. It looks like that is a problem with repositories with http auth. Maybe the error is not with http auth maybe it is related to the json formatting and the keyword "includes"
I can provide the username and password if needed.
Also I had configured a group repository including this private one. When accessing the group one i show this error in the logs
The text was updated successfully, but these errors were encountered: