On 10/5/2015 4:40 PM, Paolo Giarrusso wrote:
On Monday, October 5, 2015 at 10:21:38 PM UTC+2, Neil Van Dyke wrote:
> 'John Clements' via Racket Users wrote on 10/05/2015 03:26 PM:
> > is this what I would expect to see if a client just gave up and closed
the TCP connection before the response was written,
>
> I've seen similar errors logged by people using my SCGI package. I
> believe you're correct that it almost always means that the HTTP client
> dropped the connection. This can happen in a variety of ordinary usage
> scenarios, such as clicking a second link on the page (to load in the
> same window and tab) after the HTTP request for first link has been
> initiated by the response has not yet finished.
>
> You might want to let the exception percolate up in the code to just
> before it would be logged/reported as an error, and only then catch it.
> Maybe have that exception handler use `log-<yourmodule>-debug` or
> `log-<yourmodule>-warning`.
Could this be done by the web application framework? I imagine that's a bad
idea when programming at a very low-level (and if that's the case here, ignore
my point), but I'd certainly expect it to be automated in, say, the framework
described here: http://docs.racket-lang.org/continue/index.html. (Can't judge
the SCGI framework yet, though I'd consider the option).
I've seen this sporadically in a particular situation. YMMV.
I have a good sized middleware database application serving AJAX
requests (JSON in and out) to multiple web portals that were written at
different times by different people. One portal based on Dojo
occasionally exhibits this behavior in IE clients on some active pages
that have many AJAX calls in flight. The same code running in Chrome or
Firefox never causes the error. Another portal based on jQuery causes
no problems even where it overlaps function with the Dojo portal.
On the browser side there are no errors/warnings - the server data is
received and everything works. On the server side, it's clear that the
error occurs after the request handler has finished and the response has
been sent.
Because the error is trivially reproducible [client dropping
connection], and because in my case it seemed to be specific to the
IE/Dojo combination, I haven't pursued it much. But if I had to put
money on it, I wager on IE being the problem.
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.
