Juju doesn't send a correct close control frame when closing websocket connections.
Bug #1961192 reported by
Simon Richardson
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
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:/
| Changed in juju: | |
| assignee: | nobody → Caner Derici (cderici) |
Revision history for this message
| Caner Derici (cderici) wrote | #1 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
| Changed in juju: | |
| assignee: | Caner Derici (cderici) → nobody |
| milestone: | 2.9-next → none |
To post a comment you must log in.
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)