On 10/5/2015 11:24 PM, Paolo Giarrusso wrote:
It sounded confusing that you could close a connection "too early"
after all data was sent. But it makes some sense for AJAX with some
sort of persistent connections.
Still, no reason for error output to appear — a server has to deal
with this, as it can certainly arise with network partitions, client
crashes... even buggy clients. But the presented facts don't convince
me there's a bug with IE here, even though I'm no IE user.
It's not quite that simple.
This condition typically is caused when one side in a TCP session closes
its socket without having read all the data from the pipeline. That
causes a "connection reset" signal to be sent to the other side to
notify it that all the data was not delivered. It is technically
different from a "broken" connection which is signaled (after retries)
by failure to receive acknowledgement of sent packets. "reset" is
considered to be a rude hang-up rather than a failure per se, but it
still may pose a problem for the sender.
However the web-server and TCP library, etc. are generic: they have no
idea whether this condition is or is not an error for the application -
so if the application doesn't trap and handle it, it get reported as a
problem. But from the program's POV, in many cases the request handler
will have finished - i.e.the thread has called send/back - so there's no
way to continue.
I don't know where to put an error handler to deal with reset conditions
at the end of a request. Maybe Jay has an idea?
George
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
