-
Notifications
You must be signed in to change notification settings - Fork 30
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
Running behind reverse proxy #19
Comments
Probably fixed by accepting an environment variable for proxy endpoint, and using this to build the URL in CarterUrlExtensions.cs
|
@nivinj Im using it behind a traefik proxy, which is working fine. Maybe you have to check the passed HTTP headers |
I passing an env variable to use behind a proxy
|
If you're using nginx, make sure you're passing the host header as well - since that's what LiGet uses to resolve the absolute URL
edit: just a reminder - clear your local nuget http cache if you update this, since nuget will cache the index.json file. |
Anyone know how to do this via a kubernetes ingress-nginx config and route a subpath to the service? I tried using a generic solution I see in other articles using the rewrite-target annotation to rewrite the url, but the returning xml document doesn't include the sub path.
|
When running LiGet behind a reverse proxy, would be great if there was a way to specify the external URL to LiGet so it can be returned in the responses. In my case, I have LiGet running on
internalserver:9011
and I have apache reverse proxyingnuget.mycompany.com
tointernalserver:9011
.However in all the responses from Liget the internal (hidden) URL is used. e.g.:
{"version":"3.0.0","resources":[{"@id":"http://internalserver:9011/api/v2/package"...
Ideally should return:
{"version":"3.0.0","resources":[{"@id":"http://nuget.mycompany.com/api/v2/package"...
The text was updated successfully, but these errors were encountered: