Lines Matching +full:network +full:- +full:based

1 # Chrome Network Bug Triage : Components and labels
3 ## Some network component caveats
5 * **Internals>Network>SSL**
13 * **Internals>Network>Cache**
18 * **Internals>Network>HTTP**
23 * **Internals>Network>Logging**
25     Covers **about:net-internals**, **about:net-export** as well as the what's
28 * **Internals>Network>Connectivity**
33 * **Internals>Network>Filters**
39 ## Common non-network components
41 Bugs in these areas often receive the **Internals>Network** component, though
42 they fall largely outside the purview of the network stack team:
55     to be dangerous based on our databases, or the resulting interstitials.
56     Determination of danger based purely on content-type or file extension
67     in-memory cache, and when it's used, requests don't appear in
68     about:net-internals.  Requests for the same URL are also often merged there
73 * **Blink>Network>WebSockets**
79 * **Blink>Network>FetchAPI**
81     Generic issues with the Fetch API - missing request or response headers,
86 * **Blink>Network>XHR**
90 * **Blink>WebRTC>Network**
92     Anything WebRTC-related does not use the net stack and should go here.
106     Issues with network related extension APIs should have this component.
120 * **Internals>Media>Network**
129     also have some logic at the Internals>Network>Cache layer.
140 * **OS>Systems>Network** / **OS>Systems>Mobile** / **OS>Systems>Bluetooth**
142     These should be used for issues with Chrome OS's platform network code, and
147     CORS / Cross origin issues.  Main frame cross-origin navigation issues are
159 * **Type-Bug-Security**