Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System for meta information output options (timing, SSL info, …) #1023

Open
jkbrzt opened this issue Jan 20, 2021 · 1 comment · May be fixed by #1531
Open

System for meta information output options (timing, SSL info, …) #1023

jkbrzt opened this issue Jan 20, 2021 · 1 comment · May be fixed by #1531
Labels
needs product design We like the idea, but we want to explore the problem deeper, and consider the solution holistically

Comments

@jkbrzt
Copy link
Member

jkbrzt commented Jan 20, 2021

Meta issue for designing a system for displaying additional information to requests and responses. The current philosophy is to only show the actual HTTP exchanges so that they can be easily copied to API docs, sent elsewhere using nc, etc. The only non-http output is error messages & the download progress bar. This new system will provide a solution for showing additional metadata in a systematic and backward-compatible way.

Relevant issues:
#1011
#1007
#243
#329
#685

@jkbrzt jkbrzt added the needs product design We like the idea, but we want to explore the problem deeper, and consider the solution holistically label Jan 20, 2021
@cascadingstyletrees
Copy link

As someone who is constantly troubleshooting requests to APIs and CDN issues, seeing the SSL handshake(and even the SNI host), and certificate details are invaluable. The option to modify SNI host (like host headers), would be a unique feature that is hard to come by.

I would really appreciate more features of this type, HTTPIE is just so good, but like curl seems to output either too little or too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs product design We like the idea, but we want to explore the problem deeper, and consider the solution holistically
4 participants
@jkbrzt @BoboTiG @cascadingstyletrees and others