I have an application in which clients can upload large request entities to the server. In some situations the request will be rejected early (before the request body is totally consumed, as this may be hundreds of MB).
Is there a standard way of handling this situation? Since the rejections may happen asynchronously, I can't guarantee how much (if any) of the request body has been read. As far as I can tell from RFC 7230 section 6.5 - If the request is still in flight, we should respond early with a 'Connection: Close' (and the request stream will die as the connection closes). - If the request has been totally received, we can respond normally and reuse the connection. Is there any easy way to determine when a response is being sent early? More generally, is it even *legal* to send a response before the entire request is received *without* closing the connection? I can't really tell from the spec, but if not *it would make much more sense for akka-http to close the connection for us*. Thanks, Joe -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
