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
Option to force pretty output on response, regardless of Content-type. #92
Comments
Ah, I see this is related to #67 which seems to address this very need. Closing ticket... |
Actually, looks like that change didn't make it in. Any chance something similar could be added in? Maybe a way to override the response headers with user-specified values (similar to the headers argument, but for responses)? |
👍 |
+1 |
1 similar comment
+1 |
FWIW, i'm workarounding invalid content type responses by piping the output to jq |
see #368 |
Now with the |
Right, but there's still no way to force it, so if the Content-Type is Given the number of poorly configured REST API endpoints in the world, having the option to force/override the Content-Type seems like a valid request. |
I'm noticing a few places where the response headers are coming back with a Content-type of "text/html" when they actually contain JSON. It would be nice if, in cases like these, you could somehow specify a format to "force" on the response so that the body could still be prettified.
The text was updated successfully, but these errors were encountered: