On 09/03/2011 21:19, Adam Tauno Williams wrote: > Makes sense - these are all hosted on the same host; named based > virtual hosting is for http:// only.
Yeah. But no, we're 2011 now: SNI enables name based vhosts for https and yes it even works :) No idea if it's implemented on the host that serves pygtk.org though... > You did notice that > https://www.pygtk.org produces a certificate error? [since > 209.132.180.176 doesn't reverse to www.pygtk.org]. Yep, noticed that. Might just as well be a misconfiguration. See above. > The simple solution > [putting on my professional sys-admin hat] is not to use https:// when > accessing PyGtk docs (and there is zero reason to encrypt access to > public documentation). Sure, except that does not prevent the casual unsuspecting visitor from seeing unexpected results... For reference: a quick search shows that rt.gnome.org is used by the sysadmin team: http://live.gnome.org/Sysadmin/RequestTracker mvg, Dieter _______________________________________________ pygtk mailing list [email protected] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://faq.pygtk.org/
