Update ruleset: Omtrdc.net

[injust]

No description provided.

[J0WI]

Does this actually change/fix something?

[zoracon]

Found that regex groups become potentially problematic over time. Could you take the possible targets and list them above? Or perhaps they should rely on the wildcard above? Otherwise that would be preferred with the trivial rule <rule from="^http:" to="https:" /> still in place.

[injust]

The wildcard <target> is necessary because all subdomains exist.

I don't see a way to do the <rule>s without regex groups. We want to redirect http://a.sc.omtrdc.net but not http://a.a.sc.omtrdc.net.

[J0WI]

@injust would be great if you could have a look here.

[injust]

The existing ruleset would redirect http://a.b.d1.sc.omtrdc.net/optout.html to https://a-b.d1.sc.omtrdc.net/optout.html (note the hyphen), which is a different page.

It would also force HTTPS on a URL like http://a.b.c.d1.sc.omtrdc.net/, which is not covered by the certificate.

[ivysrono]

#17578