1 # Chrome Network Bug Triage : Components and labels
3 ## Some network component caveats
5 * **Internals>Network>SSL**
7 This includes issues that should be also tagged as **Security>UX**
8 (certificate error pages or other security interstitials, omnibox indicators
9 that a page is secure), and more general SSL issues. If you see requests
10 that die in the SSL negotiation phase, in particular, this is often the
13 * **Internals>Network>Cache**
15 The cache is the layer that handles most range request logic (Though range
16 requests may also be issued by the PDF plugin, XHRs, or other components).
18 * **Internals>Network>HTTP**
20 Typically not used. Unclear what it covers, and there's no specific HTTP
23 * **Internals>Network>Logging**
25 Covers **about:net-internals**, **about:net-export** as well as the what's
28 * **Internals>Network>Connectivity**
30 Issues related to switching between networks, `ERR_NETWORK_CHANGED`, Chrome
31 thinking it's online when it's not / navigator.onLine inaccuracies, etc.
33 * **Internals>Network>Filters**
35 Covers gzip, deflate and brotli issues. `ERR_CONTENT_DECODING_FAILED`
36 indicates a problem at this layer, and bugs here can also cause response
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:
44 * **UI>Browser>Downloads**
46 Despite the name, this covers all issues related to downloading a file
47 except saving entire pages (which is **Blink>SavePage**), not just UI
48 issues. Most downloads bugs will have the word "download" or "save as" in
49 the description. Issues with the HTTP server for the Chrome binaries are
52 * **UI>Browser>SafeBrowsing**
54 Bugs that have to do with the process by which a URL or file is determined
55 to be dangerous based on our databases, or the resulting interstitials.
56 Determination of danger based purely on content-type or file extension
57 belongs in **UI>Browser>Downloads**, not SafeBrowsing.
61 Issues submitting forms, forms having weird data, forms sending the wrong
66 Cross origin issues are sometimes loader related. Blink also has an
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
69 as well. This does *not* cover issues with content/browser/loader/ files.
71 * **Blink>ServiceWorker**
73 * **Blink>Storage>AppCache**
75 * **Blink>Network>WebSockets**
77 Issues with the WebSockets. Attach this component to any issue about the
78 WebSocket feature regardless of where the cause of the issue is (net/ or
81 * **Blink>Network>FetchAPI**
83 Generic issues with the Fetch API - missing request or response headers,
84 multiple headers, etc. These will often run into issues in certain corner
85 cases (Cross origin / CORS, proxy, whatever). Attach all components that
88 * **Blink>Network>XHR**
90 Generic issues with sync/async XHR requests.
92 * **Blink>WebRTC>Network**
94 Anything WebRTC-related does not use the net stack and should go here.
98 Sharing data/tabs/history/passwords/etc between machines not working.
100 * **Services>Chromoting**
102 * **Platform>Extensions**
104 Issues extensions loading / not loading / hanging.
106 * **Platform>Extensions>API**
108 Issues with network related extension APIs should have this component.
109 chrome.webRequest is the big one, I believe, but there are others.
111 * **Internals>Plugins>Pepper[>SDK]**
113 * **UI>Browser>Omnibox**
115 Basically any issue with the omnibox. URLs being treated as search queries
116 rather than navigations, dropdown results being weird, not handling certain
117 Unicode characters, etc. If the issue is new TLDs not being recognized by
118 the omnibox, that's due to Chrome's TLD list being out of date, and not an
119 omnibox issue. Such TLD issues should be duped against
120 http://crbug.com/37436.
122 * **Internals>Media>Network**
124 Issues related to media. These often run into the 6 requests per hostname
125 issue, and also have fun interactions with the cache, particularly in the
128 * **Internals>Plugins>PDF**
130 Issues loading PDF files. These are often related to range requests, which
131 also have some logic at the Internals>Network>Cache layer.
133 * **UI>Browser>Navigation**
135 Despite the name, this covers all issues related to page navigation, not
138 * **UI>Browser>History**
140 Issues which only appear with forward/back navigation.
142 * **OS>Systems>Network** / **OS>Systems>Mobile** / **OS>Systems>Bluetooth**
144 These should be used for issues with Chrome OS's platform network code, and
145 not net/ issues on Chrome OS.
147 * **Blink>SecurityFeature**
149 CORS / Cross origin issues. Main frame cross-origin navigation issues are
150 often actually **UI>Browser>Navigation** issues.
154 Privacy related bug (History, cookies discoverable by an entity that
155 shouldn't be able to do so, incognito state being saved in memory or on disk
156 beyond the lifetime of incognito tabs, etc). Generally used in conjunction
157 with other components.
161 * **Type-Bug-Security**
163 Security related bug (Allows for code execution from remote site, allows
164 crossing security boundaries, unchecked array bounds, etc) should be tagged