Yes, we've decided that 'failure to connect on port 80' can be ignored, but the checker is not yet updated to do that.
Alexander, feel free to remove these errors and re-enable the ruleset. Keep in mind you may have to make some other updates to bring the ruleset in line with the latest testing guidelines at https://github.com/EFForg/https-everywhere/blob/master/ruleset-testing.md. On 04/03/2015 05:09 AM, [email protected] wrote: > 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 >> [email protected] >> https://lists.eff.org/mailman/listinfo/https-everywhere > > > > > _______________________________________________ > HTTPS-Everywhere mailing list > [email protected] > https://lists.eff.org/mailman/listinfo/https-everywhere _______________________________________________ HTTPS-Everywhere mailing list [email protected] https://lists.eff.org/mailman/listinfo/https-everywhere
