URL Issue and Channel

URL

So the http://con... URL does in fact resolve when itnetkey is closed, but it gets a blank page from the firewall.

BUT this only works on port 80.

One way to fix this is to use port 443, which times out.

The better way I think is to use the return code. When hitting this when inetkey is closed, we get 200 return code (blank page), but when we hit the actual end point, we get 204 (no content).

I think this is partly how they do it, return success but no content.

Shouldn't be too hard to implement that?

Channel

Can you make the channel URL configurable through ENV variables please? Then I can set that at "deploy time" as a secret.