Upload domainflags.txt

#8
by Mittapalli - opened
Files changed (1) hide show
  1. domainflags.txt +134 -0
domainflags.txt ADDED
@@ -0,0 +1,134 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ //=========================================================================
2
+ // DOMAINFLAGS.TXT
3
+ //
4
+ // This file allows control of how DG Web Inspection Proxy
5
+ // handles HTTP and HTTPS requests made to specific web servers
6
+ //
7
+ // Current Domain Flags Definition
8
+ // (Version 9.3.0)
9
+ //
10
+ //
11
+ // Control Flag Name Parameter
12
+ // ------------------------ ---------
13
+ // SKIP INSPECTION SK
14
+ // SKIP INSPECTION if TLS TLSK
15
+ // USE BROWSER CACHING (default) CACHE
16
+ // DISABLE BROWSER CACHING NCACHE
17
+ // SKIP HTTPS SITES WHEN ACCESSED BY SAFARI TLSK_SAFARI
18
+ // SKIP HTTPS SITES WHEN ACCESSED BY CHROME TLSK_CHROME
19
+ // SKIP HTTPS SITES WHEN ACCESSED BY FIREFOX TLSK_FIREFOX
20
+ // SKIP HTTP TRAFFIC AT THE TCP LEVEL HTTP_TCPSK
21
+ // SKIP THE UPSTREAM PROXY (EXPLICIT PROXY MODE ONLY) SK_PROXY
22
+ // USE HTTP1.1 ONLY (AVOID HTTP2.0) HTTP1_1_ONLY
23
+ //
24
+ // NOTES:
25
+ // CACHE is useful to enable caching on a specific site if caching is disabled globally.
26
+ // (If caching is not disabled globally, CACHE has no effect, so can be used
27
+ // to create a domain flag entry that stops other entries from being applied.)
28
+ // If NCACHE and CACHE are both specified on the same line, NCACHE takes precedence.
29
+ // If SK or TLSK is specified all other processing is skipped, including CACHE and NCACHE.
30
+ // Add entries to the domain flags file in order of precedence.
31
+ // IP Address entries and Domain entries are treated separately.
32
+ // For each request the flags from the first matching IP address entry,
33
+ // amd the first matching domain entry are combined and applied.
34
+ //
35
+ // You can add a line to this file for each domain or IP address (range)
36
+ // that you need special handling for. Each line can contain either a
37
+ // domain entry or an IP subnet entry.
38
+ //
39
+ // Examples:
40
+
41
+ // example.com,SK //<-- SKIP inspection of requests to example.com
42
+ // example.com:80,SK //<-- SKIP inspection of requests to example.com port 80
43
+ // *.example.com,SK //<-- SKIP inspection of requests to immediate subdomains of example.com
44
+ // **.example.com,SK //<-- SKIP inspection of requests to all subdomains of example.com
45
+ // IPv4 examples
46
+ // 10.20.10.1,SK //<-- SKIP inspection of requests to the server at 10.20.10.1
47
+ // 10.10.0.0/16,SK //<-- SKIP inspection of requests to the 10.10.0.0/16 network
48
+ // 10.20.10.1:80,SK //<-- SKIP inspection of requests to the server at 10.20.10.1 port 80
49
+ // 10.20.0.0:80/16,SK //<-- SKIP inspection of requests to the 10.10.0.0/16 network port 80
50
+ // IPv6 examples
51
+ // [fe80::1c31:6bc2:7f5:675c],SK //<-- SKIP inspection of requests to the server at fe80::1c31:6bc2:7f5:675c
52
+ // [fe80::]/64,SK //<-- SKIP inspection of requests to the fe80::/64 network
53
+ // [fe80::1c31:6bc2:7f5:675c]:80,SK //<-- SKIP inspection of requests to the server at fe80::1c31:6bc2:7f5:675c port 80
54
+ // [fe80::]:80/64,SK //<-- SKIP inspection of requests to the fe80::/64 network port 80
55
+
56
+
57
+ // Domain wildcard syntax is designed to mimic directory glob syntax.
58
+ // It is not a full regular expression syntax.
59
+ // The following meta-characters are supported:
60
+ // β€’ β€œ*” will match any character except β€œ.”
61
+ // β€’ β€œ**” will match any character including β€œ.”
62
+ // β€’ β€œ?” will match a single character
63
+ // β€’ β€œ[]” can be used to specify a character match list. For example [ab] will match a or b but will not match c
64
+ // β€’ β€œ[!]” can be used to specify a negative character match list. For example [!ab] will not match a or b but will match c
65
+ // β€’ {} can be used to specify comma separated pattern alternatives. For example {ab,de} will match ab or de
66
+
67
+
68
+ // Ad networks
69
+ secure.adnxs.com,SK
70
+ as-*.casalemedia.com,SK
71
+ logx.optimizely.com,SK
72
+ fastlane.rubiconproject.com,SK
73
+ tps*.doubleverify.com,SK
74
+ timeinc-*.openx.net,SK
75
+ ads.adaptv.advertising.com,SK
76
+
77
+ // Microsoft website for AD FS
78
+ login.microsoftonline.com,SK
79
+ // Single Sign On sites
80
+ sso.teamviewer.com,SK
81
+ idp.blackberry.com,SK
82
+ pki.entitlement.siemens.com,SK
83
+
84
+ // Apple websites with certificate checks on Safari Browser
85
+ safari-extensions.apple.com,TLSK_SAFARI
86
+ icloud.com,TLSK_SAFARI
87
+ setup.icloud.com,TLSK_SAFARI
88
+ edge.icloud.com,TLSK_SAFARI
89
+ *pushws.icloud.com,TLSK_SAFARI
90
+ *contactsws.icloud.com,TLSK_SAFARI
91
+ feedbackws.icloud.com,TLSK_SAFARI
92
+ *keyvalueservice.icloud.com,TLSK_SAFARI
93
+ idmsa.apple.com,TLSK_SAFARI
94
+ **.apple.com,TLSK_SAFARI
95
+
96
+ // Salesforce caches the case files. NCACHE is needed to override caching
97
+ // if you want to log/block NTDs.
98
+ **.force.com,NCACHE
99
+
100
+ // dropbox (and others) use cache-control headers for downloaded contents. NCACHE is needed
101
+ // to override caching if you wan to log/block NTDs.
102
+ **.dl.dropboxusercontent.com,NCACHE
103
+ web.opendrive.com,NCACHE
104
+ mail-attachment.googleusercontent.com,NCACHE
105
+
106
+ // DLPTEST caches files. NCACHE is needed to override caching for logging/blocking NTDs.
107
+ dlptest.com,NCACHE
108
+
109
+ // chrome remote desktop
110
+ instantmessaging-pa.clients6.google.com,TLSK_CHROME
111
+
112
+ // Microsoft AIP / MIP (pinned certificates / tls renegotiation)
113
+ **.aadrm.com,SK
114
+ **.protection.outlook.com,SK
115
+ // Microsoft Edge sync service
116
+ edge-enterprise.activity.windows.com,SK
117
+ edge.microsoft.com,SK
118
+ // Microsoft Teams presence
119
+ **presence.teams.microsoft.com,SK
120
+ // Microsoft telemetry (teams, browser, mobile, etc)
121
+ **.events.data.microsoft.com,SK
122
+ **.events.data.msn.com,SK
123
+ *-telemetry.officeapps.live.com,SK
124
+ // Firefox telemetry
125
+ incoming.telemetry.mozilla.org,SK
126
+
127
+ // Push Notifications are often implemented by FCM.
128
+ // Fixes the case when push notifications do not appear
129
+ mtalk.google.com,SK
130
+
131
+ // SA-38414, Online commerce
132
+ cc.zdtc.app,SK
133
+ // Microsoft Teams audio connections
134
+ **.relay.teams.microsoft.com,SK