Hi Christoph - for what it's worth, I can reproduce this bug locally, using my own HomeAssistant RaspberryPi, which I view at `http://homeassistant.local:8123/core_ssh/dashboard` (and click through the https_only_mode warning page so that I can view it over insecure http) Its "web terminal" extension is broken due to this bug. When I load it with `dom.security.https_only_mode` enabled, network devtools shows a `GET` request failing, with `Scheme: wss`. When I load it without that pref enabled, my network devtools show that the corresponding `GET` request is `Schemed: ws` (not `wss`). Interestingly, when the request succeeds, it does show that the request has a `Status` of `101 Switching Protocols` (rather than e.g. 200). I'm not sure if that's relevant/interesting or not.
Bug 1701386 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi Christoph - for what it's worth, I can reproduce this bug locally, using my own HomeAssistant RaspberryPi, which I view at local insecure URL `http://homeassistant.local:8123/core_ssh/dashboard` (and I click through the https_only_mode warning page so that I can view it over insecure http, since I have the `https_only_mode` pref enabled). The HomeAssistant "web terminal" extension is broken for me, apparently due to this bug. When I load it with `dom.security.https_only_mode` enabled, network devtools shows a `GET` request failing, with `Scheme: wss`. When I load it without that pref enabled, my network devtools show that the corresponding `GET` request is `Schemed: ws` (not `wss`). Interestingly, when the request succeeds, it does show that the request has a `Status` of `101 Switching Protocols` (rather than e.g. 200). I'm not sure if that's relevant/interesting or not.
Hi Christoph - for what it's worth, I can reproduce this bug locally, using my own HomeAssistant RaspberryPi, which I view at local insecure URL `http://homeassistant.local:8123/core_ssh/dashboard` (and I click through the https_only_mode warning page so that I can view it over insecure http, since I have the `https_only_mode` pref enabled). The HomeAssistant "web terminal" extension is broken for me, apparently due to this bug. When I load it with `dom.security.https_only_mode` enabled, network devtools shows a `GET` request failing, with `Scheme: wss`. When I load it without that pref enabled, my network devtools show that the corresponding `GET` request is `Schemed: ws` (not `wss`). Notably, when the request succeeds, it does show that the request has a `Status` of `101 Switching Protocols` (rather than e.g. status `200` like most of the other requests in network devtools). I'm not sure if that's relevant/interesting or not.
Hi Christoph - for what it's worth, I can reproduce this bug locally, using my own HomeAssistant RaspberryPi, which I view at local insecure URL `http://homeassistant.local:8123/core_ssh/dashboard` (and I click through the https_only_mode warning page so that I can view it over insecure http, since I have the `https_only_mode` pref enabled). The HomeAssistant "web terminal" extension is broken for me, apparently due to this bug. When I load it with `dom.security.https_only_mode` enabled, network devtools shows a `GET` request failing, with `Scheme: wss`. When I load it without that pref enabled, my network devtools show that the corresponding `GET` request is `Schemed: ws` (not `wss`). Notably, when the request succeeds (in a build with the pref turned off), it does show that the request has a `Status` of `101 Switching Protocols` (rather than e.g. status `200` like most of the other requests in network devtools). I'm not sure if that's relevant/interesting or not.