Florian Schulze

There are many other places where the correct URL is required and ``X-Outside-URL`` is the way to go. I have this setup myself in various instances and it works correctly....

I was trying to make sure the requirements were understood correctly. That the result of ``/+api`` is used is the point. If the server and proxies in front are configured...

> My first config may appear wrong but from a user point of view it works: when I force the hostname (http://devpi) in the Devpi config file, devpi-client commands works...

The ``X-FORWARDED-PROTO`` etc headers are supported by waitress which we use as the server library, but they added a required option to trust the ip the request is coming from,...

The upcoming devpi-client 6.0.0 will warn if scheme, host or port are rewritten by the server.

See https://m.devpi.net/fschulze/dev/devpi-client/6.0.0.dev9 and https://m.devpi.net/fschulze/dev/+f/5fe/c5286f35d0d8a/devpi_client-6.0.0.dev9-py2.py3-none-any.whl

@melvyn-apryl I think the following should make the scheme always work (got it from https://github.com/devpi/devpi/issues/539#issuecomment-1236411586). If that is the case, I will add it to the example config created by...

I tested it locally with curl passing in the header and it seems to work. @melvyn-apryl Why add the $scheme to the proxy url? The devpi-server app is always listening...

There is no such option yet. I plan to improve the PyPI fetching a bit by using the provided ETags, which should make cases with no changes faster and reduce...

I took a quick look and it doesn't seem like ``pypiserver`` supports any API which would allow a better fix than your cron job idea.