I think a full flow-chart would look like a worse version of the old Florida voters' ballot joke ( ). 4), OS version, IIS version, AppPool account, other AppPool settings (Load User Profile), directory permissions, bitness (32- or 64-), various file proxy settings (ignore local-understanding local, loopback, override, machinename, restarting services, lions, tigers, bears-oh my), etc. I can't find a single document online that has working instructions (for my current setup), partly because there are so many variables, for the proxy to deal with. If I want Fiddler to "serve me" as a server-side developer, the proxy is a real hassle-due to Microsoft's choices, no fault of Fiddler's, but I still feel the pain. (I know you've commented on so many people saying "I followed the instructions, but it just doesn't work." Today, that became me.) If I want Fiddler to do (far better) what any browser's dev toolbar "just does," Fiddler is fairly easy to set up. The proxy part of Fiddler can be a real challenge at times. ![]() I hate to phrase it this way, but I want Fiddler to do what Wireshark "just does." I realize Wireshark is not a proxy. I want to capture all IIS traffic (from and to) "on the server." I don't know how to make that clearer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |