Update TI.com ruleset - #16701

Since the rule is currently disabled by default and most of the comments are severely outdated I wanted to bring it to a functional state.

These are the subdomains currently (i.e. not this PR) listed in Texas-Instruments.xml with the behaviour observed today:

Nonfunctional domains:

Problematic subdomains:

Partially covered subdomains:

Fully covered domains:
DNS entries for www.national.com point to buy.ti.com, which times out for me (might work in the US?). national.com times out for me too. However https://www.ti.com still tries to load content from national.com and national.com.ti.com (no DNS entries, probably a path error).

Insecure cookies are set for these hosts:
The current version only lists e2e.ti.com. It seems like cookies with Secure: False are set for more hosts, including .ti.com and www.ti.com.

Subdomains in targets:

And a few more already mentioned above.

TLDR: Almost all comments are outdated, (at least partially) wrong or incomplete, and should not be present in their current state. Of course it would be good to add comments describing the current state, I would argue a link to this issue would suffice for the time being.

I'd say that was quite extensive for a rule called "TI.com (partial)" 😄

I'll happily add a few more targets (after additional testing) for

• e2e-uat
• training
• focus
• myportal

, however I'd first like some feedback.

If it makes sense to add subdomains that only redirect as well (if they have valid HTTPS), I can add them too. Targets that I can't verify as working (be it due to errors or potential geoblocking) would have to be contributed by someone else.

Thanks for researching them!

We document nonfunctional/problematic in the ruleset file itself:
https://github.com/EFForg/https-everywhere/blob/master/CONTRIBUTING.md#non-working-hosts

Subdomains that only redirect should also be added as target:
https://www.eff.org/https-everywhere/faq#why-does-https-everywhere-include-rules-for-sites-like-paypal-that-already-require-https-on-all-their-pages

Targets that work neither with HTTP nor HTTPS can be removed.

Could someone take a look at this?

ERROR src/chrome/content/rules/Texas-Instruments.xml: Fetch error: http://www.ti.com/ => https://www.ti.com/: (28, 'Operation timed out after 30001 milliseconds with 0 bytes received') ERROR src/chrome/content/rules/Texas-Instruments.xml: Fetch error: http://focus.ti.com/ => https://focus.ti.com/: (28, 'Operation timed out after 30001 milliseconds with 0 bytes received') ERROR src/chrome/content/rules/Texas-Instruments.xml: Fetch error: http://fedid.ext.ti.com/ => https://fedid.ext.ti.com/: (28, 'Operation timed out after 30001 milliseconds with 0 bytes received') ERROR src/chrome/content/rules/Texas-Instruments.xml: Fetch error: http://investor.ti.com/ => https://investor.ti.com/: (28, 'Operation timed out after 30001 milliseconds with 0 bytes received')

If I'm reading it right it says that the URLs

• https://www.ti.com
• https://focus.ti.com
• https://fedid.ext.ti.com
• https://investor.ti.com

don't work (timeout). Even though some of them redirect, they work fine for me with HTTPS. Not sure what the issue is here, especially since www.ti.com worked in the CI test earlier.

They are hosted by Akamai and at times they are blocking our tests. You can add an exclusion here:
https://github.com/EFForg/https-everywhere/blob/master/utils/ruleset-whitelist.csv

Had some issues, but everything looks fine now

I'll remove focus.ti.com as a target and move it to the comments, since the issue is not limited to the main page (see http://focus.ti.com/general/docs/traininghome.tsp vs https://focus.ti.com/general/docs/traininghome.tsp)

If there's anything else, let me know