@jpmens is the authentication send to the backend server?
I have a Nginx proxy which handles basic authentication and i needed to remove the headers from the upstream request to not confuse the service running there.
@jpmens Had the same problem with Hugo’s livereload websocket. Solved it by creating a cookie after the first successful login and using that as an alternate authentication method. Not ideal at all but the only way I could find to avoid this with Safari.
@jpmens Yeah, auth/realm should probably match the other locations.
I can definitely see my cookie from my site in the Safari devtools under Storage/Cookies. No idea why it wouldn’t show up other than maybe there’s a filter applied? Although it disappears if I hit the refresh icon, weirdly, but comes back if I access the page again.
Add comment