Skip to main content

Module apps

Module apps 

Source
Expand description

Native apps and browser extensions (18.35): their requests are the site’s users, not bots, but they never load a page’s stylesheets, so the browser test can’t find them. They’re recognised here instead:

  • [traffic] apps (name=pattern, comma-separated): a pattern with :// matches the start of the request’s Origin (an extension: chrome-extension://<id>), any other pattern is looked for in the User-Agent, ignoring case (HITOP/ in HITOP/2.3 CFNetwork/…); after a pattern ending in / the version is read;
  • without a configured match, by platform: an extension Origin (chrome-extension://, moz-extension://, safari-web-extension://), Apple’s networking stack (CFNetwork/… Darwin/…, NetworkingExtension/), Android’s (Dalvik/) and Electron (Electron/) — counted under a name for the platform (“iOS/macOS app”), since anything in a request can be made up and only configured names are kept as names.

An app’s own events go to /_rws/e ([super::record::app_event]).

Structs§

App
A recognised app client.

Constants§

MAX_APPS
The most [traffic] apps entries read.

Functions§

any_configured
Whether any app is configured.
configured
Whether name is a configured app (an app’s event must name one).
detect
The app a request comes from, if any.
set_apps
Replace the configured apps (a configuration reload, tests).