Re: [Webpush] Proposed 5xx status code for WebPush

Cyrus Daboo <cyrus@daboo.name> Thu, 19 November 2015 17:00 UTC

Return-Path: <cyrus@daboo.name>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 050D21B2CD1 for <webpush@ietfa.amsl.com>; Thu, 19 Nov 2015 09:00:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.487
X-Spam-Level:
X-Spam-Status: No, score=-2.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHlNdT9Rull9 for <webpush@ietfa.amsl.com>; Thu, 19 Nov 2015 09:00:22 -0800 (PST)
Received: from daboo.name (daboo.name [173.13.55.49]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF3E61B2CC8 for <webpush@ietf.org>; Thu, 19 Nov 2015 09:00:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by daboo.name (Postfix) with ESMTP id 35CF8279BE51; Thu, 19 Nov 2015 12:00:17 -0500 (EST)
X-Virus-Scanned: amavisd-new at example.com
Received: from daboo.name ([127.0.0.1]) by localhost (daboo.name [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m129graVenmZ; Thu, 19 Nov 2015 12:00:16 -0500 (EST)
Received: from [17.149.232.135] (unknown [17.149.232.135]) by daboo.name (Postfix) with ESMTPSA id E39D3279BE46; Thu, 19 Nov 2015 12:00:15 -0500 (EST)
Date: Thu, 19 Nov 2015 12:00:12 -0500
From: Cyrus Daboo <cyrus@daboo.name>
To: Brian Raymor <Brian.Raymor@microsoft.com>, ietf-http-wg@w3.org
Message-ID: <E08800597B37897DEBEB5C64@caldav.corp.apple.com>
In-Reply-To: <BY2PR0301MB0647D01CC525FCE54B2BD033831B0@BY2PR0301MB0647.namprd03.prod.outlook.com>
References: <BY2PR0301MB0647D01CC525FCE54B2BD033831B0@BY2PR0301MB0647.namprd03.prod.outlook.com>
X-Mailer: Mulberry/4.1.0b1 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; size=909
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/M1XITcY8CTMmsBJ95C2F-lxY-Cs>
X-Mailman-Approved-At: Mon, 23 Nov 2015 13:13:50 -0800
Cc: webpush@ietf.org
Subject: Re: [Webpush] Proposed 5xx status code for WebPush
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Discussion of potential IETF work on a web push protocol <webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>, <mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>, <mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2015 17:00:24 -0000

Hi Brian,

--On November 19, 2015 at 5:19:15 AM +0000 Brian Raymor 
<Brian.Raymor@microsoft.com> wrote:

> In WebPush
> (https://datatracker.ietf.org/doc/draft-ietf-webpush-protocol/), an
> application server can request that the push service acknowledge that it
> has delivered a message to a user agent. The push service indicates
> success (positive acknowledgement) by returning a 410 (Gone) to the
> application server.

It seems a little odd for "success" to be indicated by a 4xx code. Why not 
just return a 204 (No Content) for that case?

If you do that, then you can use 410 for the case where the server has 
stopped processing the push, and 503 for the "operation" failure.

If you need more fine-grained error reporting, then consider using 
<https://tools.ietf.org/html/draft-ietf-appsawg-http-problem-01> as the way 
to do that rather than inventing lots of new status codes.

-- 
Cyrus Daboo