rnewson commented on issue #3976: URL: https://github.com/apache/couchdb/issues/3976#issuecomment-1098865348
so, two points. 1) this isn't a "crash". The erlang process specifically for the request with the malformed input terminates unsuccessfully. As the OP noted, this doesn't affect any other request or cause a server restart. This is intentionally how CouchDB (and Erlang) handles unexpected situations. 2) We should enhance the jwtf code to catch when jiffy throws an exception during decode and send a clean 400 instead. In summary, we can, and should, improve the quality of CouchDB's response to a malformed request, but there's no deeper problem for CouchDB's resilience. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
