-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Response transformer plugin causes all requests to timeout #1283
Comments
Is the response returned by the API a streaming response? |
Nope, just a basic call through to httpbin
|
Can you try to replicate this with the new 0.8.3 release? |
Has been fixed by #1263 @ThorArakis please confirm. As there is no body transform, the content-length header would be left unchanged by the plugin. Yet, the body would be parsed, and then re-jsonified. Causing a different length because of whitespace differences between the original and the re-jsonified body. |
I just pulled the latest from master and can confirm that the response transformer no longer kills the request! Thanks! |
When I have a response transformer plugin active on an endpoint it seems to cause the endpoint to stop responding, and all requests through that endpoint time out. When I disable the plugin the request start working again.
This appears to happen with all of the different configurations that I have tried on the response transformer plugin, and also happens when there is a single plugin or multiple plugins enabled on the endpoint.
plugin configuration:
The text was updated successfully, but these errors were encountered: