Last active
January 11, 2016 21:47
-
-
Save ericlaw1979/3a039dbce5c084bc0162 to your computer and use it in GitHub Desktop.
Announcement for FiddlerCore 4.6.2
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The last thing I did at Telerik was release FiddlerCore 4.6.2, available from https://www.telerik.com/fiddler/fiddlercore | |
(includes demo app) and http://www.nuget.org/packages?q=fiddlercore. | |
There are three major areas of change: | |
1> v4.6.2 now goes async (unblocking the thread) for DNS lookups and for connection reuse. This should generally improve | |
performance for Fiddler[Core], in some cases dramatically, as the .NET thread pool growth algorithm is pretty conservative. | |
While I didn't have the opportunity to finish async'ing everything I wanted to, this was a pretty solid start. | |
2> Certificate generation has changed pretty significantly, to improve performance and to accommodate changes in Certificate | |
Validation that are coming in upcoming versions of Chrome and Firefox (and presumably IE/Edge some day). In particular, | |
performance improvements come from the use of wildcard certificates and the use of CertEnroll rather than MakeCert. | |
Functional improvements come from setting the SubjectAltName field in the certificate (as Chrome and Firefox plan to | |
deprecate the SubjectCN at some unspecified point in the future, possibly in 2016). | |
If your applications are already using BCMakeCert.dll/CertMaker.dll, then simply upgrading FiddlerCore (and those libraries) | |
should get you to a good place with no fuss or muss. If, however, you are presently depending on MakeCert, there's going to | |
be some compatibility hiccups because the change to use CertEnroll by default on Win7+ means that previously-generated | |
certificates based on MakeCert are no longer going to work properly-- you'll need to remove those certificates and regenerate | |
a new root and trust that root. The process (in Fiddler itself) is described here: http://textslashplain.com/2015/10/30/reset-fiddlers-https-certificates/ but you'll need to do the equivalent cleanup in your code. | |
3> BasicFormats.dll brings the Transcoders from Fiddler (e.g. Export/Import of HAR files, Import of PCAP, etc) to FiddlerCore | |
4.6.2 users. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment