UseHTTPS is ignored when the port in a log record is unknown

[StoneSteps]

When the port in a log record is unknown or is missing (e.g. CLF logs), the value of the UseHTTPS configuration variable set to yes is ignored when rendering report links. The expected behavior is to render links with the https:// prefix if any of these conditions is true:

• The URL was requested via HttpsPort port
• UseHTTPS is set to yes and the port number was not captured in a log file.
• UseHTTPS is set to yes and the URL was requested via more than one port, but one of these ports was an HttpsPort port.

This is an example to illustrate the last point. If HttpPort is 80 and HttpsPort is 443 and

• page A was requested over port 80,
• page B was requested over port 443,
• page C was requested over ports 80 and 443,
• page D was requested over ports 80 and 8080 and
• page E was requested over ports 8080 and 443,

then when UseHTTPS is set to no, only page B will be rendered with the https:// prefix and when UseHTTPS is set to yes, pages B, C and E will be rendered with the https:// prefix.

[StoneSteps]

Fixed in v4-3 and v4-4 (default)