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
{{ message }}
This repository has been archived by the owner on Nov 8, 2024. It is now read-only.
When a curl trace file is generated going against an endpoint using HTTPS, the resulting "Send SSL data", "Recv SSL data" chunks in the tracefile cause 'noisy' output for both the --raw and --blueprint options.
Removing these chunks from the tracefile eliminates the noisy output.
Perhaps the first for loop in the parse() function (in parser.js) could filter out these chunks?
But, on a more positive node, nice tool - as the description states, "If you want a human readable form then this parser is what you need". The blueprint output is a quite nice feature.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
version 0.0.8
When a curl trace file is generated going against an endpoint using HTTPS, the resulting "Send SSL data", "Recv SSL data" chunks in the tracefile cause 'noisy' output for both the --raw and --blueprint options.
Removing these chunks from the tracefile eliminates the noisy output.
Perhaps the first for loop in the parse() function (in parser.js) could filter out these chunks?
But, on a more positive node, nice tool - as the description states, "If you want a human readable form then this parser is what you need". The blueprint output is a quite nice feature.
The text was updated successfully, but these errors were encountered: