I have an application using Flask security that decorates a route with login_required, but the login process keeps redirecting back to the login page. I suspect the problem lies in the reverse proxy architecture (internally HTTP, but externally HTTPS), but I could it do with some advice on how to debug things. Is there a way to pin down where the redirection occurs internally? Another route that uses basic authentication appears to work fine...
I have an application using Flask security that decorates a route with login_required, but the login process keeps redirecting back to the login page. I suspect the problem lies in the reverse proxy architecture (internally HTTP, but externally HTTPS), but I could it do with some advice on how to debug things. Is there a way to pin down where the redirection occurs internally? Another route that uses basic authentication appears to work fine...