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
Describe the bug
When performing requests via the perform_request method It checks if content-type is application/json, and if so - return the json parsed response.
But when response's content-type has charset specification (i.e content-type: application/json; charset=utf-8) it ignores it and return the bytes content instead of a dict. To Reproduce
Make a graphql request via IdentityProtection.
hod-alpert
changed the title
[ BUG ] json responses with charset sepcification in the content-type aren't parsed as json
[ BUG ] json responses with charset sepcification in the content-type isn't parsed as json
Jul 6, 2022
hod-alpert
added a commit
to hod-alpert/falconpy
that referenced
this issue
Jul 6, 2022
jshcodes
changed the title
[ BUG ] json responses with charset sepcification in the content-type isn't parsed as json
[ BUG ] json responses with charset specification in the content-type isn't parsed as json
Jul 7, 2022
Describe the bug
When performing requests via the perform_request method It checks if content-type is application/json, and if so - return the json parsed response.
But when response's content-type has charset specification (i.e
content-type: application/json; charset=utf-8
) it ignores it and return the bytes content instead of a dict.To Reproduce
Make a graphql request via IdentityProtection.
Expected behavior
Instead of checking exact match - checking for
application/json
prefix in the content-type header.Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: