| Summary: | HTTPS confusion between www.libreoffice.org and www.documentfoundation.orgh | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Lionel Elie Mamane <lionel> |
| Component: | WWW | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | detective.conan.1412, lohmaier, website |
| Priority: | medium | ||
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| URL: | https://www.libreoffice.org/get-help/bug/ | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
|
Description
Lionel Elie Mamane
2012-11-23 15:37:08 UTC
What's your browser and version, please? Sounds like: * http://nabble.documentfoundation.org/SSL-Problem-td3696325.html * http://nabble.documentfoundation.org/libreoffice-org-uses-an-invalid-security-certificate-td3243656.html -- please see Florian's answer (In reply to comment #1) > What's your browser and version, please? Galeon 2.0.7; based on Mozilla code; Debian package 2.0.7-2.1+b1 I'd expect SNI support comes from the underlying Mozilla code, but not 100% sure. Well, nothing that can be fixed - if SNI doesn't work reliably in the broser, then you have to live with the warnings. IPv4 addresses are all assigned, so we have to use the same address for a couple of domains. As the problem is not fixable, due to the nature of it, and since only old browser are affected → worksforme. https://sni.velox.ch/ says my browser sends TLS SNI extension in its ClientHello. And now, I can't reproduce the issue from same computer, same browser. So must have been a transient server issue :) |