• Data
• Proxy
• Events
• DNS
• Sockets
• SPDY
• HTTP Cache
• HTTP Throttling
• SPIs
• Tests
• HSTS

Current proxy settings

Proxy auto-config initialization

• View all events
• Latest proxy resolver event:

Proxies which have failed recently, and are marked as bad

Host resolver

• View pending lookups
• Default address family: (IPv6 disabled)

Host resolver cache

• Capacity:
• Time to live (ms) for success entries:
• Time to live (ms) for failure entries:

Socket pools

• May break pages with active connections
• View live sockets

SPDY Status

• SPDY Enabled: ????
• Use Alternate Protocol: ????
• Force SPDY Always: ????
• Force SPDY Over SSL: ????
• Next Protocols: ????

SPDY sessions

Alternate Protocol Mappings

Entries

Statistics

In order to prevent Distributed Denial of Service (DDoS) attacks from being perpetrated by web pages and extensions that run within Chrome, the HTTP throttling mechanism keeps track of errors requesting a given URL (minus the query parameters), and after a few 5xx errors in a row, starts exponentially increasing an interval during which requests to the given URL are disallowed.

You may enable or disable the feature below. Please let us know if the feature is causing problems for your web site. More details and contact information at http://dev.chromium.org/throttling.

Throttle HTTP requests if the server has been overloaded or encountered an error.

Layered Service Providers

Namespace Providers

How to get data for bug reports

1. Reproduce the network problem.
2. Click the Dump to text button in the Data tab.
3. Copy-paste the resulting selected text to a file.
4. Email the text file to the bug investigator, along with an explanation of what went wrong.

• The network log may contain personally identifying information like IP addresses, URLs, and cookies.
• You can edit the log to obscure information if you like, but sometimes it is relevant to the bug.
• If you choose not to have cookies removed from the log, you must toggle the checkbox before clicking the button.
• Ideally you would have the tool running before you reproduce the bug. If that isn't possible (perhaps the bug happens unpredictably), then the next best thing is to load chrome://net-internals/ as soon as you can after the problem has occurred.

How it works

• While the net-internals page is open, it will capture the network events that are happening in Chrome. You can view that in real-time by going to the Events tab.
• Once you close the net-internals window, the data it had captured will be discarded.
• Chrome keeps around a small buffer of the most recent network events even when the net-internals window is not open. That way if you open chrome://net-internals/ shortly after encountering a problem, you may still find the relevant data. These passively captured events are less accurate however, and will be prefixed in the log with (P).

Input a URL which failed to load, and then click the button to run some tests for why it failed.

HSTS is HTTPS Strict Transport Security: a way for sites to elect to always use HTTPS. See http://dev.chromium.org/sts.

Add domain

Input a domain name to add it to the HSTS set:

Delete domain

Input a domain name to delete it from the HSTS set (you cannot delete preloaded entries):

Query domain

Input a domain name to query the current HSTS set: