Does this work with both X-Scheme and X-Forwarded-Proto headers as discussed?
The proxy fix work for all standard X-Forwarded-* headers. X-Scheme is not used anywhere, X-Forwarded-Proto is more robust.
Right, but our existing code uses X-Scheme (as per old advice since removed from the Flask website - see RM3149), and users have deployments that will be setup that way. We need to fall back to X-Scheme if it is present but X-Forwarded-Proto is not, to avoid breaking their installations.
I assume (as you haven't removed it) that it works in conjunction with the existing reverse proxy code?
