Can someone explain to me why one of the travis tests fails? I don't see anything useful in the error log at https://travis-ci.org/EFForg/https-everywhere/jobs/136743355

We tend to always cover the whole *.tum.de host, not just a single subdomain.
Would you like to add others too? You can find a guide here:
https://github.com/EFForg/https-everywhere/blob/master/ruleset-style.md

I'm afraid, I cannot make any rule for the whole domain, there are too many subdomains that are not handled in a uniform way.

Please close the issue if you prefer not to have single subdomain rules.

We already have Technical_University_Munich.xml and Tum.de.xml (which seems obsolete anyway). You can add this host there.

@J0WI fixed + added some tests. Some of the certificates for TUM have expired and the tests fail. What is the best solution for this?

The best is to remove the targets/redirect rules for them and add comments on the top about their issue.

It would also be nice if you could remove the wildcard targets and replace them with the hosts that are supporting https. This would also avoid test urls and non-capturing groups.

@J0WI Fixed. Let me know if there are any more issues. Also feel-free to squash-merge.

Please use a generic <rule from="^http:" to="https:" /> to just redirecting all listed targets to https.

@jbreitbart Are you still interested in working on this?

@jeremyn Thanks for the reminder.

I rebased my fork on the current master and updated it. See comments above.

Using Sublist3r (see the style guide) I see there are many, many more tum.de domains than what you've listed here. Do you mean in #5084 (comment) that you're not interested in adding any more domains than what are already included?

@jbreitbart I'm trying to figure out what to do with this pull request. Are you interested in adding the missing tum.de subdomains?

Hi @jbreitbart, are you still interested in working on this pull request? If not, I'm going to close it.

No response, closing.