Consider a web server hosting a site (mysite.com) for which both HTTP and HTTPS are allowed. When the client browses to HTTP, he's automatically redirected to HTTPS.
I'm seeing different behavior based on whether Clear WinINET cache is used or not. On a regular capture session, following a request sent from a browser for http://mysite.com Fiddler (v4.6.2.3) shows: 200 | HTTP | Tunnel to | mysite.com:443. Next frame is 200 | HTTPS | mysite.com | / . It's like the HTTP request never exists - it's not even visible on a Wireshark capture. For the same exact request, but after clearing the WinINET cache, the output is different, with the first frame, as expected, being: 302 | HTTP | dialin.temenos.com | / . Clear the temporary internet files in IE (not Edge) doesn't result in any different outcome. It seems it's only Fiddler's magic function that does the trick.
Any idea if the WinINET cache can be cleared without using Fiddler, ideally from a browser (either IE / Chrome / etc) ?
1 Answer, 1 is accepted
I am not really sure Chrome is affected by WinINET cache. In theory Fiddler and IE should clean the cache in the same way (that's how it used to be) but something might have diverged as time passed.
I think in Firefox you could turn caching off from the developer toolbox. You might also use curl.
Regards,
Tsviatko Yovtchev
Telerik