How are networking problems tracked by mozilla.org?
Contributors should understand that the “Networking” component is only for certain “core” aspects of networking. Many bugs that look like networking problems may end up in other components. Here is a list of the more commonly mentioned components, and what belongs in them: Browser: Networking Necko issues that do not clearly belong in other “Browser” components related to networking. Includes URL schemes, URL parsing, DNS, Proxy, SOCKS, PAC. Browser: Networking:File file:/// URLs and various file I/O functions in Necko Browser: Networking:FTP ftp://URLs and FTP client behavior Browser: Networking:HTTP http://URLs and http client behavior Browser: Networking: Cache Caching of HTTP, FTP and DNS Cookies Closely related to HTTP File Handling In a nutshell, if you are not going to look at something (Layout), but save it to disk or a helper app. URL Bar If something typed in the Location bar fails, but works when put into a link, it’s not a Necko bug. Image Lib Display, caching and managemen
