Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 954A2EBFB for ; Tue, 25 Dec 2012 10:59:22 +0000 (UTC) Received: (qmail 65648 invoked by uid 500); 25 Dec 2012 10:59:21 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 65545 invoked by uid 500); 25 Dec 2012 10:59:18 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 65499 invoked by uid 99); 25 Dec 2012 10:59:16 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Dec 2012 10:59:16 +0000 Received: from localhost (HELO mail-vb0-f48.google.com) (127.0.0.1) (smtp-auth username rnewson, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Dec 2012 10:59:16 +0000 Received: by mail-vb0-f48.google.com with SMTP id fc21so8010361vbb.35 for ; Tue, 25 Dec 2012 02:59:15 -0800 (PST) MIME-Version: 1.0 Received: by 10.52.29.175 with SMTP id l15mr32164385vdh.2.1356433155162; Tue, 25 Dec 2012 02:59:15 -0800 (PST) Received: by 10.52.68.209 with HTTP; Tue, 25 Dec 2012 02:59:15 -0800 (PST) In-Reply-To: References: <1356411203.4791.yext-apple-iphone@web181704.mail.ne1.yahoo.com> Date: Tue, 25 Dec 2012 10:59:15 +0000 Message-ID: Subject: Re: Documented API does not work. From: Robert Newson To: "user@couchdb.apache.org" , Scott Content-Type: text/plain; charset=ISO-8859-1 Not the tidiest fix but it works; https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commitdiff;h=ffa34b2;hp=c4ee89eeff31501c5f90493e805324e6d437d8db On 25 December 2012 10:01, Robert Newson 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 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 wrote: >> >> If the server crashes, it's a vulnerability that needs to be fixed. >> >> Then fix it.