LiteSpeed 5.0.18 on CentOS 6.5, configured to use HTTP/2.
Are there any known issues in LiteSpeed which might cause intermittent cipher issues for Safari users?
I'm not sure where our issue is originating. Some users report problems accessing sites via Safari, getting the nsposixerrordomain error message. What makes it weird is that this issue is only happening for some users, only some of the time, and only for a specific site we host.
The site itself requires authentication via OneLogin before users can access the page, so negotiations happen using OneLogin's SSO service. (The user points the browser to the main website, it redirects them to OneLogin, etc, etc)
I suspect the problem is on OneLogin's side - issues with cipher suite configuration on some of their servers, which could explain the limited impact of this issue, but I'm not sure. The error in Safari specifically mentions the site we host, not OneLogin, but given the way redirects are happening for the OneLogin negotiation, Safari may just be reporting the site in a weird way.
Just trying to eliminate possible causes while we work to resolve this issue.
Are there any known issues in LiteSpeed which might cause intermittent cipher issues for Safari users?
I'm not sure where our issue is originating. Some users report problems accessing sites via Safari, getting the nsposixerrordomain error message. What makes it weird is that this issue is only happening for some users, only some of the time, and only for a specific site we host.
The site itself requires authentication via OneLogin before users can access the page, so negotiations happen using OneLogin's SSO service. (The user points the browser to the main website, it redirects them to OneLogin, etc, etc)
I suspect the problem is on OneLogin's side - issues with cipher suite configuration on some of their servers, which could explain the limited impact of this issue, but I'm not sure. The error in Safari specifically mentions the site we host, not OneLogin, but given the way redirects are happening for the OneLogin negotiation, Safari may just be reporting the site in a weird way.
Just trying to eliminate possible causes while we work to resolve this issue.