为什么我在 fiddler 中看不到 WCAT 流量?

发布于 2024-09-16 13:10:51 字数 814 浏览 11 评论 0 原文

我正在使用 WCAT 来负载测试我的应用程序,并且我想查看 fiddler 中的流量。

当我运行 WCAT 脚本时,它运行正常,但我在 fiddler 中看不到任何流量...我是否需要配置 fiddler 来代理 WCAT 流量?

我正在测试的网络应用程序位于我的本地计算机上,但我没有使用“localhost”对其进行寻址,而是在设置配置中使用我的计算机的名称。我也没有在 fiddler 中设置任何过滤器。

编辑:

是我正在测试的交易(ipv4.fiddler 是根据下面的建议最近添加的):

transaction
{
    id = "add a new user";
    weight = 1;

    request
    {
            verb = POST;
            postdata = "Name=Bob+Smith&Gender=M&DateOfBirth=01%2F01%2F1970&Email=testuserdude" + rand("1","1000") + rand("1","1000") + "@example.com&Password=123456&ConfirmPassword=123456";
        url         = "http://ipv4.fiddler/TokenBasedLoginTests/Account/Register";
        statuscode  = 302;
    }
    close
    {
        method      = ka;
    }
 }

谢谢马特

I'm using WCAT to load test my app, and I want to see the traffic in fiddler.

When I run the WCAT script, it runs OK,but I don't see any of the traffic in fiddler... Do I need to configure fiddler to proxy WCAT traffic?

The web app I am testing is on my local machine, but I'm not addressing it with "localhost", I'm using the name of my machine in my settings config. I don't have any filters set up in fiddler either.

EDIT:

Here's my transaction I'm testing with (the ipv4.fiddler is a recent addition as per a suggestion below):

transaction
{
    id = "add a new user";
    weight = 1;

    request
    {
            verb = POST;
            postdata = "Name=Bob+Smith&Gender=M&DateOfBirth=01%2F01%2F1970&Email=testuserdude" + rand("1","1000") + rand("1","1000") + "@example.com&Password=123456&ConfirmPassword=123456";
        url         = "http://ipv4.fiddler/TokenBasedLoginTests/Account/Register";
        statuscode  = 302;
    }
    close
    {
        method      = ka;
    }
 }

Thanks

Matt

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(4

且行且努力 2024-09-23 13:10:51

http://blogs.iis.net/thomad/archive/2010/05/11/using-the-wcat-fiddler-extension-for-web-server-performance-tests.aspx ,

WCAT 请求不会显示在 Fiddler 中
也不能使用代理服务器
WCAT。

该陈述的前一部分是由后一部分暗示的。这表明 WCAT 团队专门删除了使用代理服务器的功能,这似乎是一个奇怪的选择,但如果他们认为负载会导致代理失效,则可能是有意义的。

如果需要,您可以将 Fiddler 配置为作为反向代理运行,然后将 WCAT 指向该反向代理;然后你会看到流量,Fiddler 会将入站请求重定向到其实际目的地。请参阅http://www.fiddler2.com/redir/?id=reverseproxy

您可能会考虑使用 Visual Studio Web 测试工具,因为它们确实正确使用代理(以及 Fiddler)。

Per http://blogs.iis.net/thomad/archive/2010/05/11/using-the-wcat-fiddler-extension-for-web-server-performance-tests.aspx,

WCAT requests won't show up in Fiddler
nor can a proxy server be used with
WCAT.

The former part of that statement is implied by the latter part. It suggests that the WCAT team specifically removed the ability to use a proxy server, which seems like an odd choice, but might make sense if they thought the load would take down a proxy.

If you wanted, you could configure Fiddler to run as a reverse proxy, and then point WCAT at that reverse proxy; you'd see the traffic then, and Fiddler would redirect inbound requests to their actual destination. See http://www.fiddler2.com/redir/?id=reverseproxy

You might consider using the Visual Studio Web Test tools instead, as they do properly use the proxy (and hence Fiddler).

初与友歌 2024-09-23 13:10:51

当你使用http://ipv4.fiddler的服务器时会发生什么?本地流量不通过 Fiddler,但它在 wininet 上添加 ipv4.fiddler 作为代理(我可能会弄错,我确信 Eric Lawrence 会纠正我),因此,可以捕获当地交通?

我经常使用 Fiddler 来测试 Web 应用程序和服务,并且总是使用 ipv4.fiddler 来捕获本地流量。

希望这有帮助!

What happens when you use the server of http://ipv4.fiddler? Local traffic doesn't go through Fiddler, but it adds the ipv4.fiddler as a proxy on top of wininet (I may be getting that wrong and Eric Lawrence will correct me, I'm sure), and as a result, can capture local traffic?

I use Fiddler quite a bit to test web apps and services and always use ipv4.fiddler to capture my local traffic.

Hope this helps!

扶醉桌前 2024-09-23 13:10:51

您可以使用传输级工具(例如 Wireshark 或 Ethereal)而不是 HTTP 代理轻松跟踪 WCAT 流量(对于调试非常有用)。这些工具能够捕获网卡/数据包级别的流量。您需要做的就是...

a) 使用启用的过滤器运行捕获,以限制客户端和服务器之间的流量并使用特定协议(即 HTTP) - 总是有大量不相关的流量流过您的网络卡并添加过滤将使事情变得更容易。如果您有多个客户端,最好在服务器上运行捕获。

b) 跟踪流(通常只需单击与请求/响应相关的数据包之一并将其重建为请求/响应。

请注意,这会影响吞吐量/性能。实际运行时最好将其关闭!希望这很有帮助!

You can easily track WCAT traffic (very useful for debugging) using a transport level tool (such as Wireshark or Ethereal) rather than an HTTP proxy. These tools are able to capture traffic at the network card/packet level. All you need to do is...

a) Run a capture with a filter enabled to limit to traffic between client(s) and server and using a particular protocol (i.e. HTTP) - There's always a lot of unrelated traffic flowing through your network card and adding the filtering will make things easier. If you have multiple clients it might be best to run the capture on the server.

b) Tracing a stream (normally just click on one of the packets related to the request / response and rebuild it to a request / response.

Note that this will impact on throughput/performance. Best to turn it off for a real run! Hope this is helpful!

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文