blob: 3aaee184b98736ebdcfa2b68201e928e0c809ea5 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
<div id=capture-view-tab-content>
<b>Network events generated by the browser are being captured to this window ...</b>
<table style="margin: 15px">
<tr>
<td>Passively captured events:</td>
<td align=right id=capture-view-passively-captured-count></td>
</tr>
<tr>
<td>Actively captured events:</td>
<td align=right id=capture-view-actively-captured-count></td>
</tr>
</table>
<p>
<input type=button value="Delete all captured data" id=capture-view-delete-all />
</p>
<p><input id=capture-view-byte-logging-checkbox type=checkbox />
Include the actual bytes sent/received (may result in huge logs).
</p>
<ul>
<li>
<b>TIP</b>: <a href="#" id=capture-view-tip-anchor>logging from the command line</a>.
<div style="display:none; margin-top: 10px" id=capture-view-tip-div>
Another way to capture network events is by using the command line flag:
<blockquote>
--log-net-log=<i>FILENAME</i> [ --net-log-level=<i>NUMBER</i> ]
</blockquote>
This will stream the network events directly to a file of your choosing. If you additionally want it to log the network bytes, then pass --net-log-level=0.
</div>
</li>
</ul>
</div>
|
