Windows: Free, Cross-platform: CommercialĪlthough technically not a WDP, Wireshark deserves a mention here as another debugging tool that can sometimes be useful, however the process of decrypting HTTPS traffic is a bit more involved. There are numerous WDPs available today, a selection of which can be found below:įiddler Classic: Windows, Fiddler Everywhere: Cross-platform This can be handy in situations where the server expects some kind of encoded value but you don't know what encoding might be happening behind-the-scenes, or when you need to compare a script replay with a recording taken with the browser (most WDPs support importing HAR files). This goes for encrypted HTTPS traffic as well.Īside from providing a purpose-built UI for viewing HTTP requests and responses, WDPs also cater for an independent view of the conversation as a result of this MITM approach. Assuming traffic is flowing through the proxy (we'll get to that in a bit), the HTTP data will be visible for you to inspect. In hacker/technical terms, this is the Man-In-The-Middle (MITM) approach. In essence, a WDP puts itself into the middle of the conversation between the client (like your browser, k6, or any proxy-aware application running on your machine) and the server. Doing so can be challenging when relying purely on console.log statements or using -http-debug=full, and so this article presents another way of showing the HTTP traffic: using a web debugging proxy. HTTP conversations can be quite complex, particularly when dealing with website HTTP traffic (as opposed to APIs) and when there is a sequence of requests taking place with dynamic identifiers (in other words, Correlation).ĭebugging HTTP requires looking at a lot of places to see what could be going wrong. You start wondering: why on earth is that? Other times, you'll run your script and see it receive the expected responses (usually HTTP 200), yet the "thing" your script is meant to create simply doesn't show up anywhere, like on the database or as a record on the site. When you run your scripts, you may observe unexpected error status codes (typically in the 4xx-5xx status code range). One of the more challenging aspects of load testing happens very early on: getting your scripts working.
0 Comments
Leave a Reply. |