You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to debug when things go wrong, it would be useful to be able to analyze the traffic in Wireshark. Of course, in general this traffic will be encrypted. However, Wireshark supports reading in the encryption key and decrypting the traffic: https://wiki.wireshark.org/TLS. It would be great if HTTP.jl could optionally write out those keys so we can look at the traffic in wirewhark.
The text was updated successfully, but these errors were encountered:
In order to debug when things go wrong, it would be useful to be able to analyze the traffic in Wireshark. Of course, in general this traffic will be encrypted. However, Wireshark supports reading in the encryption key and decrypting the traffic: https://wiki.wireshark.org/TLS. It would be great if HTTP.jl could optionally write out those keys so we can look at the traffic in wirewhark.
The text was updated successfully, but these errors were encountered: