Description: <div style="text-align: justify;">We use a lot of applications which work and communicate over the Internet - download managers, browser plugins, media players etc. Some of them use well documented protocols and others use proprietary protocols to communicate with their servers. So, how does one go about figuring out what's actually happening under the hood? How are these programs communicating? which protocols are they using? This video hopes to get you started into investigating and understanding how a network utility works under the hood. We will use a popular Download Manager program as the case study.<br><br>We all know that download managers work by requesting small parts of a file simultaneously. But how many of us know exactly what in the HTTP protocol allows this? In this video, we will learn how to reverse engineer the traffic and headers to figure out that it is the "Range" header field in the HTTP GET request that makes this magic possible! <br><br>We leave it as an exercise to the user, to reverse engineer the Alexa toolbar and see how it works. The solution to this will be posted in the next video! <br><br><br></div><br><style type="text/css"> body { background: #FFF; } </style>
Tags: basics ,
Disclaimer: We are a infosec video aggregator and this video is linked from an external website. The original author may be different from the user re-posting/linking it here. Please do not assume the authors to be same without verifying.