> On November 18, 2018 at 2:48 PM Andrea Pescetti <pesce...@apache.org> wrote:
> > For debugging, I suggest using cURL instead of OO, for example: > > curl -sviI https://www.openoffice.org/ > > Thanks, if the issue is with SSL this indeed helps in finding more > details. Still, curl will always work also on affected systems, so if it > is SSL-related it won't be enough to check whether the site uses a > wildcard SSL certificate... Maybe some more technical certificate details? I compared the output from the sites that do work curl -sviI https://fosdem.org/2019/ curl -sviI https://www.google.com/ fosdem specifies < Content-Type: text/html; charset=utf-8 google specifies < Content-Type: text/html; charset=ISO-8859-1 However the AOO site does not specify any charset. Could that be the problem? On funny note, the issuer of the Google certificate is * issuer: C=US,O=Google Trust Services,CN=Google Internet Authority G3 Regards, Pedro --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
