-
Notifications
You must be signed in to change notification settings - Fork 837
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
204 response with non-zero content-length takes too long to finish #5818
Comments
@adachenski Is there a publicly accessible endpoint we can use to replicate this issue? |
@adachenski could you send us a screen grab of the response headers after this happens? |
@numaanashraf there are no publicly accessible endpoints for the calls that I'm testing |
@adachenski This seems to be due to a non-zero Content-Length being sent by the server for 204. Postman would wait for the response from the server (as indicated by the content-length). The request will finally finish when the underlying connection is closed by the client or server. Refer related issue at #2418 (comment) for more details. I'll keep this issue open to discuss how we'ld like to handle such cases. |
I've just encountered this as well. @numaanashraf This indeed seems to happen due to a non-zero Content-Length in reply Header, which in my case is true. |
Closing this as duplicate of: #2418 |
To Reproduce
Expected behavior
Actual behavior
Right after sending the request the app hangs
App hangs JPG
Than it takes very long to execute(1 min)
Long to execute JPG
Other Rest API client example(execution time 31ms)
Other client JPG
Environment
Postman Version: 6.7.1
OS: Windows 7, MAC OS 10.14
The text was updated successfully, but these errors were encountered: