Also, I found out some interesting stuff about an undocumented Zune API - also through inspecting existing transfer logs. Some time to set up an environment and you will be ready to intercept incoming content. Capture interesting stuffįor example Windows Phone applications that come as XAP packages. Packet data is also really interesting to look at, especially if it goes through SSL - WireShark has pretty decent tools to cover those details too (just look at the hex table). In many cases it reveals details I did not expect to see.ĭetailed data might include source port, target port, target and source IPs as well as some details about the actual physical network controller handling the processing. Although it might seem that the initial returned data set is quite complicated (and trust me, there is a lot of un-needed junk captured), you can easily set specific filters to only see what you need. Have you ever had issues controlling the traffic flow - maybe you were calling a service but weren't sure that the requests went the right way? What about malformed HTTP requests? If any (or both) of the situations are familiar to you, then WireShark is there to help. So what are some uses that might potentially benefit the people who decided to install it? Personally I have three main reasons, and i am describing those below. And although I never used it on anything but my Windows PC, it's a really interesting tool to have installed - both for developers and curious minds. One of these tools is WireShark - a network protocol analyzer For Windows and *nix systems.
There are tools out there that have their value severly underestimated.
0 kommentar(er)
