NGINX configuration for TLS-only-via-redirect breaks operation behind reverse proxy #4
Description
Commit ea9d7ca sets up NGINX so that plain HTTP is always redirected to HTTPS. This breaks using the Composefile provided here behind a reverse proxy which already terminates TLS and forwards HTTP.
While TLS-only-via-redirect makes sense for production setups, I would argue that production setups will usually terminate TLS elsewhere anyway. For testing purposes, it seems preferrable to allow as many usage scenarions as possible, i.e. not trying to enforce a possibly not-even-configured TLS setup. (One could of course replicate the per-component/per-service forwarding done via the NGINX configuration directly in that TLS-terminating proxy, but that seems like unnecessarily strong coupling to the internals of an InGrid installation.)
For our test environment, we currently resort to reverting to the previous NGINX configuration, c.f. https://gitlab.opencode.de/umwelt-info/infrastruktur/testbetrieb/-/merge_requests/360. We would be glad if this repository could be switched to a more flexible NGINX setup.