Trying to get some loose-ends fixed with our Caddy configuration.
We have several IoT devices that can be linked to one another via Caddy reverse proxy.
One option is to remote to an upstream server.
We can do that, but then the api calls for the upstream server have double forward-slashes (//) which cause a 404.
This use to work with our Nginx configuration. I am not sure if Nginx cleaned up the URI or what, but I am hoping there is something similar for Caddy that I have missed.
After remoting using revers proxy, I see this in chrome URL bar:
But in devtools, I see this:
Is there anything that can help? Some switch that can take care of URL normalization?