Fiddler 无法从 ASP.NET 网站嗅探 SOAP 流量
到目前为止，我已经成功使用 fiddler 从测试装置、控制台应用程序和 Web 项目中嗅探 Web 服务流量。
今天我注意到，如果我运行 Web 应用程序（它是一个 ASP.NET 网站，托管在 IIS 本地），我将无法再嗅探此类流量。我看到所有本地流量，但 Web 服务流量消失了（服务正在受到攻击，因为我确实看到代码中的响应调试）。
我仍然能够在同一解决方案（完全相同的环境）中成功嗅探来自测试装置或控制台应用程序的肥皂请求和响应。
如果它是 Windows（我使用的是 Win7）安全更新或类似的更新，我猜它永远不会起作用（除非它只影响通过 IIS 路由的流量）。
我应该寻找什么可能导致出现此行为？
任何指示表示赞赏！
注意：我可以看到本地流量，但看不到对不在本地托管的 Web 服务的 SOAP 请求/响应（它是另一个团队提供的沙箱）
编辑：这一点配置成功了（在 Rick Strahl 的博客上找到）
<system.net>
<defaultProxy>
<proxy
usesystemdefault="False"
bypassonlocal="True"
proxyaddress="http://127.0.0.1:8888"/>
</defaultProxy>
</system.net>
So far I've been successfully using fiddler to sniff web service traffic from both test fixtures, console apps and web projects.
Today I noticed I am not able anymore to sniff that kind of traffic if I am running my web application (it's a ASP.NET website, hosted locally on IIS). I see all the local traffic but the web service traffic is just gone (the service is being hit as I do see the response debugging into the code).
I am still able to successfully sniff soap requests and responses from test fixtures or console apps in the same solution (exact same environment).
If it was a windows (I am on Win7) security update or the likes it would never work I guess (unless it affects only traffic routed through IIS).
What should I be looking for that could cause the emergence this behavior?
Any pointers appreciated!
NOTE: I can see local traffic, but not the SOAP request/responses to the web service which is not hosted locally anyway (it's a sandbox another team is providing)
EDIT: This bit of configuration did the trick (found on Rick Strahl's blog)
<system.net>
<defaultProxy>
<proxy
usesystemdefault="False"
bypassonlocal="True"
proxyaddress="http://127.0.0.1:8888"/>
</defaultProxy>
</system.net>
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
您可以尝试以下操作 -
Can you try the following -
Web 服务的客户端是什么？ ASP.NET？
除非您将 ASP.NET 配置为使用代理，否则 ASP.NET 流量不会被代理。 app.config 或 machine.config 是否可能发生更改，导致流量不再被代理？
您应该查看此部分：http://www.fiddlerbook。 com/fiddler/help/hookup.asp#Q-DOTNET
What's the client of the web service? ASP.NET?
ASP.NET traffic isn't proxied unless you configure ASP.NET to use a proxy. It's possible/likely that the app.config or machine.config changed such that traffic is no longer getting proxied?
You should have a look at this section: http://www.fiddlerbook.com/fiddler/help/hookup.asp#Q-DOTNET
如果您想在开发计算机上查看网站和 Web 服务之间的 http 流量，并且不想更改 machine.config。
一种简单的解决方案是更改网站的应用程序池标识，以使用您自己的当前登录用户的凭据。这意味着您的网站将采用您的代理设置，并且现在将重定向到 Fiddler。
If you want to view the http traffic between your web site and your web service on your development machine, and don't want to change your machine.config.
One easy solution is to change the Application Pool Identity of your web site to use your own credentials of the current logged on user. This means that your web site will adopt your proxy settings and will now redirect to Fiddler.
确保您正在调用的 Web 服务（从 IE）不是 http://localhost/yourwebservice
Fiddler 不会拦截 localhost来自 IE 的流量，请改用 http://machinename/yourwebservice。
Make sure the web service you are calling (from IE) is not http://localhost/yourwebservice
Fiddler will not intercept localhost traffic from IE, use http://machinename/yourwebservice instead.
大约一周前我遇到了这个问题。试试这个页面： http://docs.telerik.com/fiddler/Observe-流量/故障排除/NoTrafficToLocalhost
http:// www.fiddler2.com/fiddler/help/hookup.asp#Q-LocalTrafficipv4.fiddler 是对我有用的部分。希望这有帮助。
I ran into this issue a week or so ago. Try this page: http://docs.telerik.com/fiddler/Observe-Traffic/Troubleshooting/NoTrafficToLocalhost
http://www.fiddler2.com/fiddler/help/hookup.asp#Q-LocalTrafficThe ipv4.fiddler was the part that worked for me. Hope this helps.
对于这些 http 请求，您可能使用 80 以外的端口。我记得设置了一个反向代理来查看我在开发期间在本地计算机上发出的 WCF 请求。这是文档：
http://www.fiddlertool.com/fiddler/help/reverseproxy.asp
You're probably using a port other than 80 for these http requests. I remember setting up a reverse proxy to look at WCF requests I was making on my local machine during dev. Here's the documentation:
http://www.fiddlertool.com/fiddler/help/reverseproxy.asp