To avoid confusing upstream proxy servers if the port is defined
as well as the protocol we remove the port if it is 443 and we
have defined the protocol to be https.
The reason for this change is that when running Clair behind
Envoy the vhost lookup failed when the port as also included
in the host header.
The call to Clair with klar and the same call using curl can
be seen here below, the additional port caused the vhost
lookup to fail. Not defining the port at all would mean that
we get the default port, 6060, for which Envoy is not listening.
To avoid confusing upstream proxy servers if the port is defined as well as the protocol we remove the port if it is 443 and we have defined the protocol to be https.
The reason for this change is that when running Clair behind Envoy the vhost lookup failed when the port as also included in the host header.
The call to Clair with klar and the same call using curl can be seen here below, the additional port caused the vhost lookup to fail. Not defining the port at all would mean that we get the default port, 6060, for which Envoy is not listening.