Christian,
Unfortunately due to request pipelining (the norm in HTTP/1.1), any
attempt to send an error message or abort just results in the container
having to silently consume the body of the upload anyway. The next
request in the pipeline after a medium size upload could even
conceivably be in the same TCP packet, so the container has to consume
every request to make sure it correctly locates the start of the next
request.
It isn't worth even trying to handle - it's a necessary evil, the
flipside of the taken-for-granted speed boosts that request pipelining
brings.
Rick
Christian Kindler wrote:
Hi all,
there seems to be no possibility to immediately cancel a (multipart)
post request (for example if the content-length exceeds a certain
limit). Whatever I do in a servlet's doPost method (throwing an
exception, closing the request's stream, interrupting the current
thread), the client continues sending the data to the server.
So there is nothing I can do to prevent users from sending huge amount
if data to the server and producing a lot of traffic.
All I want to do is to cancel a request immediately. I don't care if
the client get's a reasonable error message or if the connection
remains or not. Is there any way to achieve this or is it a general
problem of the HTTP protocol?
I hope it's o.k. that I ask this question here, on the users list
unfortunately nobody could help or explain the reasons for this behavior.
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
