> The problem is that the client never receives a response from the server and remains blocked waiting for a response.
What client are you using? Many "traditional" clients, like Java HttpURLConnection will not attempt to read the response until their request has been fully read by the server. In the case of a "413 too large", the server will not read the request, but will still return a response. This can appear like the server has not responded. (The Akka-HTTP client can read the response in these cases.) See https://github.com/akka/akka/issues/18203#issuecomment-139192071 for a related discussion re aborting large uploads part-way through the upload stream (e.g. when an error is found part-way through the upload). Uploading an isolated repro case may help clarify exactly what problem you are seeing and help others to suggest workarounds. Best, Rich On Thursday, September 17, 2015 at 6:01:20 PM UTC+1, Konrad Malawski wrote: > > Hey again, > I ran a test using a very simple server and I can not reproduce the > problem you describe, everything works as expected, > see a detailed response: https://github.com/akka/akka/issues/18509 > > Could you provide a reproducer which would show when this does not work as > expected? > Thanks in advance! > > -- Konrad > -- >>>>>>>>>> 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.
