An application support specialist would find this tool useful to intercept HTTPS traffic on a local machine. Its purpose would be to enable the technician to perform various tasks from the client’s perspective as well as modifying the server’s responses prior to displaying contents on a user’s browsing session. This could be also be used to developers in lieu of a built-in IDE to view the result of a program on a browser.
Fiddler:
– fiddler2.com to download and install
– Run Fiddler > run Chrome/IE > navigate to any website
– Inspectors tab: views
– Transformer: view response body info with or without compression
– Headers
– TextView
– ImageView
– HexView
– WebView
– Auth
– Caching
– Cookies
– Raw
– Json
– XML
– Statistics tab
– Select all sessions > view summary info about request count, unique hosts, bytes sent/received, and graphical presentation of data
– AutoResponse tab
– Allow fiddler to respond on behalf of web server which is useful to troubleshoot whether client handles responses appropriately
– Replay web traffic
– Composer tab
– Build raw HTTP requests
– Fiddler Script
– Open rules file to extend fiddler UI, modify request and headers.
– QuickExec box: allows user to execute commands
– Example: setting break point of an HTTPS session at css loading by using “BPU css” at the prompt. Then, one can tell the program to break or continue to completion in returning contents to the browser. If desired, css could be removed or modified before sending to browser for quick assessment on the resulting output
