Bug #22801
closed
Spice connection with websockets encryption
Description
When websockets_encryption is set to true on foreman 1.16 spice doesn't work because JavaScript ./app/assets/javascripts/spice.js (line 5) have hardcoded schema "ws://" that in this case should be "wss://". Websockets encryption is required to have spice working on Chrome (version 64.0.3282.140) without additional configuration as it by default refuses to connect to websockets without encryption and truted certificate. File is unchanged in current head.
Updated by Rafał Ramocki about 6 years ago
- Subject changed from Spice connection websockets encryption to Spice connection with websockets encryption
Updated by Ohad Levy almost 5 years ago
an example for such code could be found at https://gitlab.freedesktop.org/spice/spice-html5/blob/master/spice_auto.html#L98
Updated by The Foreman Bot almost 3 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ewoud Kohl van Wijngaarden
- Pull request https://github.com/theforeman/foreman/pull/8515 added
Updated by Ewoud Kohl van Wijngaarden almost 3 years ago
- Triaged changed from No to Yes
- Found in Releases 1.2.0 added
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/foreman/pull/8698 added
Updated by Ewoud Kohl van Wijngaarden over 2 years ago
- Target version set to 3.0.0
Merged for 3.1.0 but I think it can be picked to 3.0.0. Setting target version so we don't forget.
Updated by Ewoud Kohl van Wijngaarden over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|10d5e55cfe544507bdd5287e1323fbf02e06b2ca.
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/foreman/pull/8717 added
Updated by Tomer Brisker over 2 years ago
- Fixed in Releases 3.0.0 added
- Fixed in Releases deleted (
3.1.0)