Nigel Metheringham <nigel@???> (Mi 10 Feb 2016 22:05:57 CET):
> Suspect you may have something like a https-everywhere plugin on your
> browser pushing it to an https URL.
An incognito tab of my Chrome browser tries to complete exim.org as
https://exim.org and offers "use tab to search bugzilla"…
Indeed it's a nice feature, but more likely it should work for searching
the documentation, shouldn't it?
And even when I type there
www.exim.org, the Chrome browser tries to
contact
https://www.exim.org, which fails, because of the certificate
problem.
Shouldn't we provide a unified view to
https?://(www\.)?exim\.org
And put the bugzilla to some
https://bugs.exim.org/.
With a redirect from the
http://bugs.exim.org/ (TLS should be enforced
because we send passwords there.)
> We do not serve the base website (exim.org or www.exim.org
…
> I've currently no intention of changing this unless there is a strong
> argument to do so (argument to not do so is key management is a pain).
It would cost us two certs.
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: F69376CE -
! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -
