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
When Content-Length mismatch happens with the provided value being bigger than the real value the connection is not closed.
The response is still correct with Content-Length: 26.
In this case meinheld, gunicorn and socketify would close the connection.
fastWSGI close the connection in this case, socketify also does this, and I think is better to close and emit a warning when Content-Length mismatch happens.
But in case the Content-Length is bigger than the real response, I think that should be better to also close the connection to keep the same behavior and to warn that something that the user/framework wants to send will not be sent.
The text was updated successfully, but these errors were encountered:
When Content-Length mismatch happens with the provided value being bigger than the real value the connection is not closed.
The response is still correct with Content-Length: 26.
In this case meinheld, gunicorn and socketify would close the connection.
If the real response is bigger than the Content-Length provided, meinheld and gunicorn will just end the response when reaches the length provided.
fastWSGI close the connection in this case, socketify also does this, and I think is better to close and emit a warning when Content-Length mismatch happens.
But in case the Content-Length is bigger than the real response, I think that should be better to also close the connection to keep the same behavior and to warn that something that the user/framework wants to send will not be sent.
The text was updated successfully, but these errors were encountered: