Fiddler is a very effective tool when it comes to troubleshooting HTTP & HTTPS issues… It’s basically a local proxy that intercepts all HTTP/HTTPS traffic either from all applications or just the application you configure it to… Fiddler configures itself as a local proxy on port 8888, processes traffic from the client application and then forwards it to the web server so it behaves like any proxy server except that it displays all information in the client application & allows for on the fly HTTPS decryption without the need for server certificate to decrypt traffic.
Troubleshooting a specific TCP session in a Wireshark packet capture should be an easy or difficult task depending on the nature of the problem that’s being investigated, what can be cumbersome is actually finding that session in the middle of a huge capture file or even a running capture with...
Whenever there is slowness issue to be investigated, the first thing to be usually checked is packet drops or high latency along the path, tools like traceroute (or tracert on windows) and nping are usually enough to draw a map of the traffic path and in some cases are enough to find out at which hop of the path we start to see a huge difference in a packet’s RTT (Round Trip Time), while the traditional traceroute may be more than adequate for a lot of cases, there are sometimes when additional proof is needed to confirm the root cause of the problem.
Recent Comments