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
>
>
>
> My question here is: What to do about this?
> Does this mean we can remove thes
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 gu
Hello list,
i was thinking about creating rules that cover the zam network.
One rule for each subsite they run was the first idea, since some big
companies like google also have multiple rules already in HTTPS-Everywhere.
Then i thought, some of the content-cdn is shared, so one rule for all
the si
We don't have any official guidelines for that yet, and the behavior
varies a lot.
Things to consider:
- If all domains are operated by the same company, they are likely to
all support HTTPS or not in similar ways, which favors combining them.
- If one domain breaks, are the others likely to bre
