I have a long-running http server process, and I get a lot of error output that looks like this:
fprintf: output port is closed context...: /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:52:0: output-response-head33 /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:23:0: output-response/method /home/clements/racket/collects/racket/contract/private/arrow-val-first.rkt:265:18 /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/share/pkgs/web-server-lib/web-server/private/dispatch-server-with-connect-unit.rkt:125:8 fprintf: output port is closed context...: /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:52:0: output-response-head33 /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:23:0: output-response/method /home/clements/racket/collects/racket/contract/private/arrow-val-first.rkt:265:18 /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/share/pkgs/web-server-lib/web-server/private/dispatch-server-with-connect-unit.rkt:125:8 fprintf: output port is closed context...: /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:52:0: output-response-head33 /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:23:0: output-response/method /home/clements/racket/collects/racket/contract/private/arrow-val-first.rkt:265:18 /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/share/pkgs/web-server-lib/web-server/private/dispatch-server-with-connect-unit.rkt:125:8 fprintf: output port is closed context...: /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:52:0: output-response-head33 /home/clements/racket/share/pkgs/web-server-lib/web-server/http/response.rkt:23:0: output-response/method /home/clements/racket/collects/racket/contract/private/arrow-val-first.rkt:265:18 /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/collects/racket/private/more-scheme.rkt:162:2: select-handler/no-breaks /home/clements/racket/share/pkgs/web-server-lib/web-server/private/dispatch-server-with-connect-unit.rkt:125:8 I took a look at this code, and it looks like this is what happens when the web-server tries to write the response and the output port is closed. I am by no means an HTTP/TCP expert, so I thought I’d ask: is this what I would expect to see if a client just gave up and closed the TCP connection before the response was written, or should this not occur in the course of normal http traffic? Thanks! John -- 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.
