mixing HTTP and HTTPS forwards in one/two relays about relayd HOT 1 OPEN

I started to read a lot of posts and I was beginning to believe that mixing the client relay was just unsupported. I've come to the conclusion this is definitely a bug.

Common with everyone else's experience the BLAST table which is not TLS enabled seems to open the connection to the server as TLS... even though it does not have "with tls"

relay "https" {
    listen on $ipv4 port https tls
    protocol "https"
    forward with tls to <www> port 8443 check https "/" code 200
    forward to <blast> port 1900 check http "/" code 401
}

However, when I added TLS to my "blast" app server...I received more/similar errors even though my app server was ok. (tested from the CLI). Then I added the "with tls" to the blast relay and VOILA it started working.

relay "https" {
    listen on $ipv4 port https tls
    protocol "https"
    forward with tls to <www> port 8443 check https "/" code 200
    forward with tls to <blast> port 1900 check https "/" code 401
}

Without "with tls" and app server running in plain http... The relay log suggested "TLS handshaking" error.

Without "with tls" and the appserver running https... the relay log suggested "tlsv1 allert protocol, version"

But when I added "with tls" and had the server running https.... all was fine.

This suggests that mixing is not possible or a bug and/or "with tls" is not completely documented.

from relayd.