rtrbt
commented
6 months ago Sorry, investigating this took a bit. This is a (12 years old!) bug in WebKit (Safari's browser engine): https://bugs.webkit.org/show_bug.cgi?id=80362: WebKit does not use cached credentials if a WebSocket handshake gets a 401 response. For "normal" HTTP requests this works, but for the WebSocket handshake the browser immediately asks for credentials without checking the cache.
On macOS there is a work-around: If you press cancel when Safari asks for credentials the second time (or after reloading the page or restarting Safari). Safari will retry the request with the cached credentials. Unfortunately this does not work on iOS. I'm not sure if there is anything we can do to fix this. Maybe when we have implemented #76, we could switch to HTTP Basic Auth (we use Digest Auth at the moment to not send passwords via plain HTTP) but it looks like Safari has problems with that as well.
tillsteinbach
alexander-zimmermann
On Safari (both Mac OS and iOS) I need to type in my password after every reload of a page of the web interface. On safari for iOS I also need to type in the credentials two times. After getting through the login I can browse through the web interface until I press the "reload" button again, or the page is reloaded by the browser. At the same time using chrome on Mac OS is working very fine. On my iPhone this bug is pretty annoying. Is there any information I can help with to fix this?
Best, Till