-
Notifications
You must be signed in to change notification settings - Fork 445
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
Handle compressed responses #282
Comments
@karamazov1 Yes, it can handle, could you please provide the URL you're testing? |
@Huachao this is an internal api. I know it worked in the past but also know microsoft also enabled compression on their responses recently. GET https://xxxxxxx.azure-api.net/product/products/213140 HTTP/1.1 |
@can you confirm with other tools that the response is a valid JSON |
I tried this same request using postman and the proper json is rendered. Not sure what the difference could be, no differences at the request level that I can see. Thanks for your responses, this is not critical by any means and I was just curious if compressed responses were handled as this same request was working before and I'm not sure if an extension update could be the culprit or a change on the back end endpoint broke my tests. |
What's the content encoding header of the response |
@karamazov1 thanks, I can repro this issue, I will fix it ASAP. |
@karamazov1 I have fixed the bug and will publish this fix in next release. |
Just ran into this issue myself also. When is the next release? |
@karamazov1 @offero I have published the new release 0.20.3, and you can try the new version to verify |
This is working for me now. Thanks! |
Does this extension handle compressed responses? When I tried, I get "The content type of response is application/json, while response body is not a valid json string"
The text was updated successfully, but these errors were encountered: