- From: Rafał Ruciński <notifications@github.com>
- Date: Sat, 04 Jun 2016 05:37:57 -0700
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc:
Received on Saturday, 4 June 2016 12:38:32 UTC
Thanks for the quick response! Actually, the server should be able to responsd whenever, shouldn't it? For example there's an nginx setting [client_max_body_size](http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size) that makes it respond with a 413 error after reaching the limit, but before the full request body was transferred. Correct me if I'm wrong, but the problem was on the client side, which would not allow reading the response before the whole body was sent. If fetch resolves after the response headers are sent, then I should be able to cancel the request on the client side. That's cool! --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/issues/315#issuecomment-223753453
Received on Saturday, 4 June 2016 12:38:32 UTC