Juju doesn't send a correct close control frame when closing websocket connections.

[Simon Richardson]

Closing a websocket that is initiated from the server doesn't send a status. Any websocket closure that doesn't have a status returns a 1005 code, which is classified as an abnormal closure. This can be seen in pylibjuju in quite a few places and is considered as a bad actor.

See websocket documentation for more information: https://datatracker.ietf.org/doc/html/rfc6455#section-7.1.5

[Caner Derici (cderici)]

Just to clarify here, the code we see in the client errors is 1006, which indicates that Juju doesn't even send the close control frame. (1005 is for the case where we do have a closing frame, but no status code in it)

[Canonical Juju QA Bot (juju-qa-bot)]

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.