[HTTPS-Everywhere] failed ruleset test

[sjw at gmx.ch]

I think we considered somewhere, that this kind of failure can be ignored.
@Jacob are the tests already updated for that?



Am 02.04.2015 um 16:00 schrieb Alexander Buchner:
> I saw the comments in Bahn.de.xml
>
> <!--
> Disabled by https-everywhere-checker because:
> Fetch error: http://fahrkarten.bahn.de/ =>
> https://fahrkarten.bahn.de/: (7, 'Failed to connect to
> fahrkarten.bahn.de port 80: Connection refused')
> Fetch error: http://grosskunden.bahn.de/ =>
> https://grosskunden.bahn.de/: (7, 'Failed to connect to
> grosskunden.bahn.de port 80: Connection refused')
>
> -->
>
> My question here is: What to do about this?
> Does this mean we can remove these target hosts in the rule because
> they don't answer on port 80 but they do answer on 443?!
>
> Or how can I rewrite this rule that this comment won't be added the
> next time https-everywhere-checker runs?
> _______________________________________________
> HTTPS-Everywhere mailing list
> HTTPS-Everywhere at lists.eff.org
> https://lists.eff.org/mailman/listinfo/https-everywhere


-------------- 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/20150403/9064de98/attachment.sig>