On 05/04/2011 08:39 PM, Alexander Bokovoy wrote: > >> There seem to be some misconfiguration of SSL setup at meego.com. I > >> tried with QtWebkit and it also unable to reach and render it. > > Looking into a network trace I can see that Firefox 4 talks TLSv1 to > meego.com while QtWebkit uses SSLv3. > > This actually is how its intended, bugs.meego.com is a TLS-SNI website (SSL named Vhosting): (read about it here: http://en.wikipedia.org/wiki/Server_Name_Indication).
The reason its TLS-SNI primarily is that we want to be good citizens and conserve IPs. We also can't get more to dedicate to each SSL site. If you connect to some of our services you'll get a self-signed SSL certificate when TLS-SNI support is not available in your user-agent. If you hit this URL you'll be served a help page that talks about this: https://140.211.166.236/TLS-SNI.html Primarily the complaints about this have come from people using Internet Explorer on Windows XP which led us to ask, why are you accessing our site with such an old software stack? If you hit bugs.meego.com with a TLS-SNI enabled browser you will see a correctly issued SSL Certificate. If you do not you'll get the help page if you were to accept the SSL warning and view the page. meego.com has a dedicated IP and does not use TLS-SNI for its SSL. Bugs.meego.com is not down, so hope this clears it up. Adam Gretzinger MeeGo Project Intel Open Source Technology Center _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
