You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(hunchentoot:redirect ...) redirects to HTTP even when the Hunchentoot web application is served by a reverse proxy that uses HTTPS. If I place a Nginx reverse proxy in front of a Hunchentoot web app, and configure Nginx to serve the web application using HTTPS, Hunchentoot will not know to use HTTPS when redirecting. This is because Hunchentoot does not look at the Forwarded and/or X-Forwarded-Proto HTTP headers that provide information about which protocol Hunchentoot should be using to redirect.
(hunchentoot:redirect ...)
redirects to HTTP even when the Hunchentoot web application is served by a reverse proxy that uses HTTPS. If I place a Nginx reverse proxy in front of a Hunchentoot web app, and configure Nginx to serve the web application using HTTPS, Hunchentoot will not know to use HTTPS when redirecting. This is because Hunchentoot does not look at theForwarded
and/orX-Forwarded-Proto
HTTP headers that provide information about which protocol Hunchentoot should be using to redirect.(This bug report is based on this Stack Overflow question: How to redirect to HTTPS when Hunchentoot is behind a reverse proxy)
The text was updated successfully, but these errors were encountered: