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

docker run -ti -d --env https_proxy=http://myproxy.com

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

proxy_set_header Host            $host;
proxy_set_header X-Forwarded-For $remote_addr;

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.

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: http-ingress
  annotations:
    nginx.ingress.kubernetes.io/enable-cors: "true"
    nginx.ingress.kubernetes.io/rewrite-target: /$2
spec:
  ingressClassName: public
  rules:
  - host: mydomain.com
    http:
      paths:
      - path: /nuget(/|$)(.*)
        pathType: Prefix
        backend:
          service:
            name: liget
            port:
              number: 9011