Closed jerrywoo96 closed 1 week ago
Hello
but this is not true, using the selector of json:$.hello
I get 3
which is expected, even tho the content returned is text/plain
the filter
further
thanks
ahh my mistake, you get text/html
let me test..
Works fine when the server returns text/html
also
Version and OS 0.45.24 on linux/docker
Is your feature request related to a problem? Please describe. Received Content-Type is text/html, so it is parsed as text. < This is expected.
I want to override the content type so it can be parsed as json, as the body content is a json string, so that i can use jsonPath selectors. Since the Content-Type received is text/html, i cannot use jsonPath selectors on the json body as it is not parsed as json.
Describe the solution you'd like Add Content-Type Override. Or add parse response as json checkbox feature.