Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.protocols.tcp-ip    |    TCP and IP network protocols.    |    14,669 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 13,642 of 14,669    |
|    Jorgen Grahn to Frank Swarbrick    |
|    Re: error handling for HTTP/1.1 chunked     |
|    08 Oct 10 11:30:47    |
      From: grahn+nntp@snipabacken.se              On Thu, 2010-10-07, Frank Swarbrick wrote:       > Is there a guideline on how to handle errors on the server when the       > application generating the response fails for some reason? Is closing the       > connection the only option to signify to the client that the server process       > has failed?              What does "failed" mean here? If the HTTP server crashes, the socket       is gone no matter what you do.              Or does it run some CGI script which crashes? In that case I'd say       that http://example.org/foo.cgi is what it is, even if it's garbage       and error messages. You asked for the resource, and you got it. It       just didn't look like you hoped it would.              /Jorgen              --        // Jorgen Grahn |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca