| ... | ... | @@ -3,9 +3,9 @@ |
|
|
|
Application definitions are configured using a proprietary file format. Comment lines begin with a `#` hash. Every configuration line begins with 3-character type followed by one or more colon-delimited values. The currently supported types are:
|
|
|
|
|
|
|
|
- `app:<id>:<tag>` Application definitions.
|
|
|
|
- `dom:<id>:<domain>` Bind a domain to an application definition.
|
|
|
|
- `dom:<id>:<domain>` Associate a domain to an application definition.
|
|
|
|
- `xfm:<id>:<search>:<replace>` Adds an application domain transform regular expression.
|
|
|
|
- `net:<id>:<address>` Bind a network address (in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)) to an application.
|
|
|
|
- `net:<id>:<address>` Associate a network address (in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation)) to an application.
|
|
|
|
|
|
|
|
## Applications
|
|
|
|
|
| ... | ... | @@ -18,7 +18,7 @@ Application definitions consist of two value fields: |
|
|
|
|
|
|
|
## Domains
|
|
|
|
|
|
|
|
Any number of domains can be associated to an application. To associate a domain, set the application's `<id>` in the first value fields followed by a `<domain>` in the second field.
|
|
|
|
Any number of domains can be associated to an application. To associate a domain, set the application's `<id>` in the first value field followed by a `<domain>` in the second field.
|
|
|
|
|
|
|
|
The Agent will extract domain hostnames from various protocols (eg: HTTP/S, M/DNS, SSDP, etc). After a domain has been associated, the Agent will search for matches starting with the full domain and then down each level until the root-level domain is reached. For example:
|
|
|
|
|
| ... | ... | @@ -69,4 +69,4 @@ The original input domain text is not modified by the transform, so "`instagram. |
|
|
|
|
|
|
|
## Network Addresses
|
|
|
|
|
|
|
|
Applications can be associated with entire network blocks down to a single IP address. To bind a network address to an application, specify the application `<id>` in the first value field. Specify the network's IPv4 or IPv6 `<address>` in the second field. Use [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation) to bind blocks of IP addresses. If no prefix length is specified, it is assumed to be a single address (a prefix length of `/32` or `/128` depending on IP version). |
|
|
\ No newline at end of file |
|
|
|
Applications can be associated with entire network blocks down to a single IP address. To associate a network address to an application, specify the application `<id>` in the first value field. Specify the network's IPv4 or IPv6 `<address>` in the second field. Use [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation) to associate blocks of IP addresses. If no prefix length is specified, it is assumed to be a single address (a prefix length of `/32` or `/128` depending on IP version). |
|
|
\ No newline at end of file |
