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). -- 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.
