Check HTTP return code on WebSocket transport vs WebSocket URL on universal transport

[oberstet]

Bug Description

check what crossbar returns when doing a plain HTTP/GET without a WebSocket upgrade header for both transports of type:

• websocket
• universal

that should be identical? just rendering a HTML page (which it does).

but it might be HTTP 426 versus HTTP 200!

check!

Checklist

• I have searched existing issues to avoid duplicates
• I have provided a minimal reproducible example
• I have included version information
• I have included error messages/logs