| OLD | NEW |
|---|
| (Empty) | |
| 1 <!DOCTYPE HTML> |
| 2 <html> |
| 3 <!-- Copyright (c) 2011 The Chromium Authors. All rights reserved. |
| 4 Use of this source code is governed by a BSD-style license that can be |
| 5 found in the LICENSE file. |
| 6 --> |
| 7 <head> |
| 8 <include src="../content_security_policy.html"/> |
| 9 </head> |
| 10 <body> |
| 11 <div id=howtoDumpForBugsHelpContent> |
| 12 <h2>How to get data for bug reports</h2> |
| 13 |
| 14 <ol> |
| 15 <li>Reproduce the network problem.</li> |
| 16 <li>Click the <i>Dump to file</i> button in the <i>Data</i> tab.</li> |
| 17 |
| 18 <li>The log file will act like a normal download.</li> |
| 19 |
| 20 <li>Email the log file to the bug investigator, |
| 21 <b>along with an explanation of what went wrong, including any relevant |
| 22 URLs.</b> |
| 23 You may want to compress the file before sending, as the log files can be |
| 24 fairly large but compress well. |
| 25 </li> |
| 26 |
| 27 </ol> |
| 28 |
| 29 |
| 30 <ul> |
| 31 <li>The network log <b>may contain personally identifying information</b> like |
| 32 IP addresses, URLs, and cookies.</li> |
| 33 <ul> |
| 34 <li>You can edit the log to obscure information if you like, but sometimes it |
| 35 is relevant to the bug. If you choose do this, please make sure you can still |
| 36 load the log file.</li> |
| 37 <li>If you choose not to have cookies removed from the log, you must toggle |
| 38 the checkbox before clicking the button.</li> |
| 39 </ul> |
| 40 <li>Ideally you would have the tool running <b>before</b> you reproduce the |
| 41 bug. |
| 42 If that isn't possible (perhaps the bug happens unpredictably), then the |
| 43 next best thing is to load chrome://net-internals/ <b>as soon as you can |
| 44 after</b> the problem has occurred.</li> |
| 45 </ul> |
| 46 |
| 47 <h2>How it works</h2> |
| 48 |
| 49 <ul> |
| 50 <li>While the net-internals page is open, it will capture the network events |
| 51 that are happening in Chrome. You can view that in real-time by going to |
| 52 the <i>Events</i> tab.</li> |
| 53 <li>Once you close the net-internals window, the data it had captured will be |
| 54 discarded.</li> |
| 55 <li>Chrome keeps around a small buffer of the most recent network events |
| 56 even when the net-internals window is not open. That way if you open |
| 57 chrome://net-internals/ <b>shortly after</b> encountering a problem, |
| 58 you may still find the relevant data. |
| 59 These <i>passively captured</i> events are less accurate however, and will |
| 60 be prefixed in the log with <span style="font-family: monospace;">(P)</span>. |
| 61 </li> |
| 62 </ul> |
| 63 |
| 64 <button id="popup-close-button">Close this popup</button> |
| 65 </div> |
| 66 <script src="chrome://resources/js/util.js"></scirpt> |
| 67 <script src="chrome://net-internals/help.js"></script> |
| 68 </body> |
| 69 </html> |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 7455005:
Apply content-security-policy to chrome://net-internals. (Closed)
Base URL: svn://svn.chromium.org/chrome/trunk/src/