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
{{ message }}
Repository navigation
Consider delaying (buffering) outgoing responses until request is complete in #273
Some Browsers consider a request failed when a response is sent before the entire request has gone out. We may want to look into delaying (buffering) outgoing responses until the complete request has been received.
Once #259 is in, this is less of an issue, because we default to buffering the whole incoming request first before invoking the request handler. However, this can still easily be reproduced by using the StreamingServer (see example 1).
This ticket exists for the reference, to document this behavior and as an RFC for future changes.
Now that #259 is in, this is no longer an issue for me personally.
I'm closing this for now as it hasn't received any input in a while and I have no plans to change this myself anytime soon. Please come back if you feel this is still an issue and we can reopen this 👍
Activity
clue commentedon Mar 20, 2018
Now that #259 is in, this is no longer an issue for me personally.
I'm closing this for now as it hasn't received any input in a while and I have no plans to change this myself anytime soon. Please come back if you feel this is still an issue and we can reopen this 👍