support for internal hostnames about http-observatory-cli HOT 1 CLOSED

To answer my own question and if anyone else is wondering. Yes, this great tool does support internal hostnames and if you have deployed the web component then as long as you update the js scripts to point to your local endpoints you should be good.

For the CLI, need to make sure the environment variables are set correctly for the user. I used the following to set permanent for httpobs user and not only the session. This will force the httpobs command to use the local api rather than the public api.

1. Switch User: su - httpobs
2. Create Env variable: echo export HTTPOBS_API_URL=http://localhost:57001/api/v1 >> ~/.bashrc
3. Load the changes: source ~/.bashrc
4. Verify: printenv

Make sure your local api is already running then execute: httpobs internal-host.com

Currently it doesn't work with internal ip's or names like "localhost" or "intranet" otherwise it works just fine for internal lab environments as long as they have a hostname i.e. staging.internalname.com etc.

oh and any sites internal or external with tls client authentication will be treated as site down, reasonably so.

from http-observatory-cli.