This is exciting because your code works.Thank you very much.
I am still working on the ideas provided by Simeon to solve my problem. With your help, I believe I can succeed soon.Later, if I
encounter problems, I will timely feedback.Now, I have a problem and I need your help.
After studying HTTPS and how fiddlercore works, I have a question: after a successful handshake, does the client, fiddlercore, and
server use the same symmetric secret key?Is the client data received by fiddlercore encrypted after fiddlercore proxies the client?
Based on the knowledge acquired, I think that the client, fiddlercore and server use the same symmetric secret key, and fiddler's
data is not encrypted. Fiddler caches the request data, then encrypts it and sends it to the server.Am I wrong?
As far as I know, fiddler does not support any mechanism for sending HTTP requests "streaming" to the server because the
requests are read from the client -- requests are always cached before they are sent (except websocket).Will the request take
longer?In practice, I had a request to send multiple images, and the whole process slowed down significantly after using fiddler. I
think that's probably the reason.Is there a way to solve this problem?Because I want to use fiddler without affecting the session (I
just want to copy the content of HTTPS requests and responses, not change it).