Well it wasn't Alex, it was me who used the term 'crash', as that is what the log said.
In my defense I don't live and breath HTTP. And I'm rolling my own interface from HTTP client code that I have used for over a decade. So I expected the transfer encoding header that I've seen from every other server, and an HTTP error if the request isn't correct. At least I now know what is going on, and can move past this log jam. Merry Christmas. Scott 'Sent from my iPhone'... Not someone else's. On Dec 25, 2012, at 4:01 AM, Robert Newson <[email protected]> wrote: Crashing a single erlang process is a far cry from crashing the server, Alex. :) "Then fix it" Scott is right that we should return well-formed error responses and not stack traces (We're not J2EE, for goodness sake) but some error conditions get missed. Admonishing those that report errors is not kind, nor in the spirit of our community. Omitting the leading slash in the path of an HTTP request line is pretty unusual these days (because it's mandatory and almost everyone uses a library of some sort) but that's just a fancy way of saying it's a blind spot in our (well, mochiweb's) error handling. Quite fixable. Merry Christmas! B. On 25 December 2012 04:53, Scott <[email protected]> wrote: See the pasted in log. It says 'crash'. But really appears to be an exception trap. Although I would expect to get an error in return for a malformed request. 'Sent from my iPhone'... Not someone else's. On Dec 24, 2012, at 9:54 PM, Mark Hahn <[email protected]> wrote: If the server crashes, it's a vulnerability that needs to be fixed. Then fix it.
