如果您使用的是 Mac，则以上都不是。使用 Charles 代理。这是我遇到过的最好的网络/请求信息收集器。您可以查看和编辑所有传出请求，并根据响应的类型以多种形式查看这些请求的响应。许可证费用为 50 美元，但您可以下载试用版，看看您的想法。
如果你使用 Windows，那么我会继续使用 Fiddler。
None of the above, if you are on a Mac. Use Charles Proxy. It's the best network/request information collecter that I have ever come across. You can view and edit all outgoing requests, and see the responses from those requests in several forms, depending on the type of the response. It costs 50 dollars for a license, but you can download the trial version and see what you think.
If your on Windows, then I would just stay with Fiddler.
fiddler 的“自定义规则”功能在任何 http 调试器中都是无与伦比的。编写代码来实时操作 http 请求和响应的能力对于我和我在 Web 开发中所做的工作来说是无价的。
fiddler 有很多功能是 charles 所没有的，而且很可能永远不会有。 Fiddler 领先数光年。
Fiddler is the winner every time when comparing to Charles.
The "customize rules" feature of fiddler is unparalleled in any http debugger. The ability to write code to manipulate http requests and responses on-the-fly is invaluable to me and the work I do in web development.
There are so many features to fiddler that charles just does not have, and likely won't ever have. Fiddler is light-years ahead.
I use both Charles Proxy and Fiddler for my HTTP/HTTPS level debugging.
Pros of Charles Proxy:
Handles HTTPS better (you get a Charles Certificate which you'd put in 'Trusted Authorities' list)
Has more features like Load/Save Session (esp. useful when debugging multiple pages), Mirror a website (useful in caching assets and hence faster debugging), etc.
As mentioned by jburgess, handles AMF.
Displays JSON, XML and other kind of responses in a tree structure, making it easier to read. Displays images in image responses instead of binary data.
如果您正在开发使用 AMF 传输数据的应用程序（在特定的一组< a href="http://help.arcgis.com/EN/arcgisserver/10.0/apis/rest/index.html" rel="nofollow">GIS Web API 我经常使用），Fiddler 目前不支持提供 AMF 解码器，使您能够以易于阅读的格式轻松查看二进制数据。 Charles 提供了这个功能。
If you're developing an application that transfers data using AMF (fairly common in a particular set of GIS web APIs I use regularly), Fiddler does not currently provide an AMF decoder that will allow you to easily view the binary data in an easily-readable format. Charles provides this functionality.
Wireshark, Firebug, Fiddler all do similar things - capture network traffic.
Wireshark captures any kind of network packet. It can capture packet details below TCP/IP (HTTP is at the top). It does have filters to reduce the noise it captures.
Firebug tracks each request the browser page makes and captures the associated headers and the time taken for each stage of the request (DNS, receiving, sending, ...).
Fiddler works as an HTTP/HTTPS proxy. It captures every HTTP request the computer makes and records everything associated with it. It does allow things like converting post variables to a table form and editing/replaying requests. It doesn't, by default, capture localhost traffic in IE, see the FAQ for the workaround.
The benefit of WireShark is that it could possibly show you errors in levels below the HTTP protocol. Fiddler will show you errors in the HTTP protocol.
If you think the problem is somewhere in the HTTP request issued by the browser, or you are just looking for more information in regards to what the server is responding with, or how long it is taking to respond, Fiddler should do.
If you suspect something may be wrong in the TCP/IP protocol used by your browser and the server (or in other layers below that), go with WireShark.
发布评论
评论（7）
如果您使用的是 Mac，则以上都不是。使用 Charles 代理。这是我遇到过的最好的网络/请求信息收集器。您可以查看和编辑所有传出请求，并根据响应的类型以多种形式查看这些请求的响应。许可证费用为 50 美元，但您可以下载试用版，看看您的想法。
如果你使用 Windows，那么我会继续使用 Fiddler。
None of the above, if you are on a Mac. Use Charles Proxy. It's the best network/request information collecter that I have ever come across. You can view and edit all outgoing requests, and see the responses from those requests in several forms, depending on the type of the response. It costs 50 dollars for a license, but you can download the trial version and see what you think.
If your on Windows, then I would just stay with Fiddler.
与 Charles 相比，Fiddler 每次都是赢家。
fiddler 的“自定义规则”功能在任何 http 调试器中都是无与伦比的。编写代码来实时操作 http 请求和响应的能力对于我和我在 Web 开发中所做的工作来说是无价的。
fiddler 有很多功能是 charles 所没有的，而且很可能永远不会有。 Fiddler 领先数光年。
Fiddler is the winner every time when comparing to Charles.
The "customize rules" feature of fiddler is unparalleled in any http debugger. The ability to write code to manipulate http requests and responses on-the-fly is invaluable to me and the work I do in web development.
There are so many features to fiddler that charles just does not have, and likely won't ever have. Fiddler is light-years ahead.
为了补充该列表，还请注意 http://mitmproxy.org/
To complement the list, also be aware of http://mitmproxy.org/
我使用 Charles Proxy 和 Fiddler 进行 HTTP/HTTPS 级别的调试。
Charles 代理的优点：
Charles Proxy 的缺点：
I use both Charles Proxy and Fiddler for my HTTP/HTTPS level debugging.
Pros of Charles Proxy:
Cons of Charles Proxy:
如果您正在开发使用 AMF 传输数据的应用程序（在特定的一组< a href="http://help.arcgis.com/EN/arcgisserver/10.0/apis/rest/index.html" rel="nofollow">GIS Web API 我经常使用），Fiddler 目前不支持提供 AMF 解码器，使您能够以易于阅读的格式轻松查看二进制数据。 Charles 提供了这个功能。
If you're developing an application that transfers data using AMF (fairly common in a particular set of GIS web APIs I use regularly), Fiddler does not currently provide an AMF decoder that will allow you to easily view the binary data in an easily-readable format. Charles provides this functionality.
Wireshark、Firebug、Fiddler 都做类似的事情——捕获网络流量。
Wireshark 捕获任何类型的网络数据包。它可以捕获 TCP/IP 下面的数据包详细信息（HTTP 在顶部）。它确实有过滤器来减少它捕获的噪音。
Firebug 跟踪浏览器页面发出的每个请求，并捕获关联的标头以及请求每个阶段（DNS、接收、发送...）所花费的时间。
Fiddler 用作 HTTP/HTTPS 代理。它捕获计算机发出的每个 HTTP 请求并记录与之相关的所有内容。它确实允许将后变量转换为表格形式以及编辑/重播请求之类的操作。 默认情况下，它不会捕获 IE 中的本地主机流量，请参阅常见问题解答以了解解决方法。
Wireshark, Firebug, Fiddler all do similar things - capture network traffic.
Wireshark captures any kind of network packet. It can capture packet details below TCP/IP (HTTP is at the top). It does have filters to reduce the noise it captures.
Firebug tracks each request the browser page makes and captures the associated headers and the time taken for each stage of the request (DNS, receiving, sending, ...).
Fiddler works as an HTTP/HTTPS proxy. It captures every HTTP request the computer makes and records everything associated with it. It does allow things like converting post variables to a table form and editing/replaying requests. It doesn't, by default, capture localhost traffic in IE, see the FAQ for the workaround.
WireShark 的好处是它可以向您显示 HTTP 协议以下级别的错误。 Fiddler 将向您显示 HTTP 协议中的错误。
如果您认为问题出在浏览器发出的 HTTP 请求中，或者您只是在寻找有关服务器响应内容或响应需要多长时间的更多信息，那么 Fiddler 应该这样做。
如果您怀疑浏览器和服务器（或下面的其他层）使用的 TCP/IP 协议可能有问题，请使用 WireShark。
The benefit of WireShark is that it could possibly show you errors in levels below the HTTP protocol. Fiddler will show you errors in the HTTP protocol.
If you think the problem is somewhere in the HTTP request issued by the browser, or you are just looking for more information in regards to what the server is responding with, or how long it is taking to respond, Fiddler should do.
If you suspect something may be wrong in the TCP/IP protocol used by your browser and the server (or in other layers below that), go with WireShark.