[HTTPS-Everywhere] browser side failure correction and failed ruleset test

[sjw at gmx.ch]

Hi list

The https-everywhere-checker disabled some rulesets, because he could
not resolve host 'host.TLD':
Fetch error: http://host.TLD/ => https://www.host.TLD/: (6, 'Could not
resolve host: host.TLD')

But the browser ties to reconnect using 'www.host.TLD'. Should we let
the browser do this redirect itself (and redirect again to https) or
should we overwrite this redirect and directly connect to 'https://www.'?

Another problem that I found are incomplete certificate chains. The
browser correct them with an extra download, but
https-everywhere-checker returns:  60, 'SSL certificate problem: unable
to get local issuer certificate'

This should return a warning instead of an error.


Regards,
Jonas

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <https://lists.eff.org/pipermail/https-everywhere/attachments/20150215/ada3bd18/attachment.sig>