I doubt, there is a way to fix the integration checks. In fact, you did just what the integration test should detect: Changes to arbitrary files in the server. So, it works just as expected.
I am not aware of any way to disable the checks selectively. That would be no good idea anyway (you tend to forget to reset the list). The best way was to fix that upstream in the server code and wait for the update.
This is inside k8s. Are you suggesting to wrap apache in another apache? Doable i guess, but I’m worried there will be new broken configs that we can’t work around this way
PS: The header is not misconfigured as it uses HTTP (without S). There, of course no encryption enforcement must be done. This is part of the HTTPS server settings.
OK, so you have one container in Kubernetes that runs the NC server. Still, there is no HTTPS termination yet. So, where are the SSL certificates manages?
Typically there is a reverse proxy in front of your containers that does the SSL handling and passes on only unencrypted connections. On this point, the header should be set. A quick glance at some google results brought up ingress as a keyword.
yes termination is part of ingress.
could you point me to the docs that say we must run a another proxy in front of apache?
we’re required to follow the official documentation.