[digitalsushi]

Are there any modern tricks for debugging against a TLS website? Last time I was doing it 5 years ago we did mitm proxies, ssl self-signed tricks, to get wireshark able to sniff and read the payload.

Did anyone invent an easy way to do this?

[JBReefer]

What are you reading that you can't read in the dev tools? You can see, edit, resend, and copy requests as CURL commands in both Firefox and Chrome. You can also see timing, some encryption stuff, and it's all in plaintext because it hasn't gone over the wire yet.

[digitalsushi]

Ah, I remember. I had the model wrong. I was trying to view the HTTP payload of a remote client connecting to a remote server. We were trying to debug what was happening when clients were connecting to some enterprise appliances we didnt have the keys for. It has nothing to do with web development, but I mis-remembered what it was I used to work on. Ooops!

[NegativeLatency]

Safari has the ability to copy as curl now too.

[bendecoste]

charles proxy is not bad .. still have to do some self-signed stuff but it is fairly automated