Omni CMS: broaden the dom selector to match any OU Campus path

[danielserranoh]

Omni CMS (Modern Campus, formerly OU Campus) matched only via a dom selector pinned to a specific OU Campus version:

a[href*='a.cms.omniupdate.com/11/']

Installs served under a different path or version are missed. This broadens the selector to the host itself:

a[href*='cms.omniupdate.com']

Per review feedback, the originally proposed html patterns have been dropped — this is now a one-line dom change.

---

Test websites:

• https://www.stonybrook.edu/
• https://www.fau.edu/
• https://www.aamu.edu/
• https://www.wilkes.edu/

Assisted by Claude Code.

[tunetheweb]

I’m not sure we need this since HTTP Archive only uses Wappalyzer with DOM detection.

Can you explain more why it’s needed?

[danielserranoh]

You're right — for HTTP Archive's DOM-based detection the existing dom rule already fires, so the html patterns are redundant for that crawl. Two things prompted the PR:

1. The existing dom selector is pinned to a specific OU Campus version: a[href*='a.cms.omniupdate.com/11/']. Installs served under a different path (other versions, or the omniupdate.com/XSL/Variables include) are missed even with DOM detection. If useful, I'd rather broaden the dom rule — e.g. a[href*='cms.omniupdate.com'] — since that's the change that actually improves detection here.
2. The html form was aimed at response-first consumers of this dataset that match raw HTML without a headless browser and so can't evaluate dom rules (my use case is an internal fingerprint engine). I understand if that's out of scope for a set tuned to HTTP Archive's DOM crawl.

Happy to convert this to a broadened dom rule and drop the html additions — or close it if the response-first angle isn't something you want to carry here. Which would you prefer?

[tunetheweb]

Happy to broaden the DOM rule.

So you’re using this Wappalyzer code outside of HTTP Archive and that’s why you want to make the change? The HTML selector is deprecated and is known to be slower so don’t really want to spread usage of it much further. Saying that if it’s one these three extra ones I don’t think that’ll cause any issue. But I wouldn’t want to apply this more widely to all DOM selectors.

[danielserranoh]

Thanks — that's the useful half of the change, so I've pushed it: the html patterns are gone and the selector is now a[href*='cms.omniupdate.com'] instead of a[href*='a.cms.omniupdate.com/11/']. One-line diff; title and description updated to match.

Yes — the response-first angle was for an internal engine that consumes these fingerprints without a headless browser. Point taken on html being deprecated and slower; I'll keep those supplements on my side rather than push them here, and I'm closing the Liferay and Wagtail PRs for the same reason. Thanks for taking the time to explain the reasoning.