When using the module in basic auth systems which is mostly only test but can only be in production produces false green and false red results.
The executablePhp check is always green because the basic auth and the header check is always red because of it.
Run tests in basic auth protected system.
Add basic auth config to httpClient calls and add a check of a file which should always be accessible to identify the basic auth problematic.
As far as I know there is no core standard config for local basic auth credentials. For example the entity_print.print_engine.dompdf can be used with basic auth by config and added by settings.php
$config['entity_print.print_engine.dompdf']['settings']['username'] = '{{ access_user }}';
$config['entity_print.print_engine.dompdf']['settings']['password'] = '{{ access_pass }}';
Especially as a security oriented module we should encourage people to also use settings.local.php outside web root. We can maybe avoid UI form to force.
Active
3.0
Code
I encountered the same issue - header check is always failing for my basic auth protected site:
Hello @c-logemann since it's been a few months wonder if you want me to un-assign?
@smustgrave Sorry I was to busy in last time. Especially this issue is easy to solve when maintainer decides how to manage credentials.