IETF Logo Mail Archive

Re: [Webpush] Require the TTL header

Benjamin Bangert <bbangert@mozilla.com> Fri, 05 February 2016 16:55 UTC

Return-Path: <bbangert@mozilla.com>
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 087021B3B8C for <webpush@ietfa.amsl.com>; Fri, 5 Feb 2016 08:55:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 RudVkP1VBQ3S for <webpush@ietfa.amsl.com>; Fri, 5 Feb 2016 08:55:45 -0800 (PST)
Received: from mail-yk0-x233.google.com (mail-yk0-x233.google.com [IPv6:2607:f8b0:4002:c07::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D30501B3B8B for <webpush@ietf.org>; Fri, 5 Feb 2016 08:55:44 -0800 (PST)
Received: by mail-yk0-x233.google.com with SMTP id r207so62671029ykd.2 for <webpush@ietf.org>; Fri, 05 Feb 2016 08:55:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WbMGGw10LyP31iajB+9R7wfeLXFopJMLwGoMOWY66yE=; b=b+Y58mII/4Ei/O1tAtxrfkA/S0XDeXYzFG8w2HSpp46OamDU3sTSYSWxDuBqqNbXin a0uql3a/B0apaOF/zGR5N+t0dzcww3wLXdARZbmY+TRlEExX0HH7a2aU2xLOIuwRMCrj 8mdCeEzqAC3jR+krIK9QraoIC4AutvNFdCQa4VsYy7Ev6254B74is+XT5c/anRhTBMRN jIiia8EQJNIgfGRy4IQagdqMDKO6kP0imi+HUwqLgn6DMeFo/WmVphw6R9cOh2TRdBZf +9ctNhPUsPTrl07X+W852YHGUa6J6DOSvmYkjoqOUTG+NH1nrHe6Ya7x2UwUVhJD3dfB FxvA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WbMGGw10LyP31iajB+9R7wfeLXFopJMLwGoMOWY66yE=; b=D12AATo7sDVILgbwVCKXjxRQok9XcUpLtlGHVVeMEf2ofbiR8OT+pQAxeA7CBsUaXL BlFt/+pVAAw5v3vmuLP63InXs+ClZMR9MK/RMiemNNxhNBWYvXhgHyEsTGLldho+Q4QI lk7th8mFznk/2T9t2XmyC7QS96C/XwvtaZFIipIrUI9EnMUUpH0TvWmq/m7vK1FJirOR qM8vEMMcVwrtynawjhI2uO3ph1QYBYiFFuYwaqKb3NKEVKOpKmqXSmtPqZwf11QPQ2tS lLubol8OEVhBENGRbinvkpK5aKAoBFuYqlGOQqWwsVjXB7l2+/a0mapG8p9o0zwlSn3j bbgA==
X-Gm-Message-State: AG10YORbmKPkbxxXFbCH9ht6LZU/S68cd0O0wPOQHp9yklFPZAt0d7RWgwzWUr0Gd3xqCYBD9QIkOiVZWllqN6UO
MIME-Version: 1.0
X-Received: by 10.37.2.23 with SMTP id 23mr4723782ybc.15.1454691344064; Fri, 05 Feb 2016 08:55:44 -0800 (PST)
Received: by 10.37.196.68 with HTTP; Fri, 5 Feb 2016 08:55:43 -0800 (PST)
In-Reply-To: <BY2PR0301MB06477C93FA8937F0ABD4393383D20@BY2PR0301MB0647.namprd03.prod.outlook.com>
References: <CABp8Eu+oBj8XKWbqd9ypT_mQWzMxXDe+cBR_vqk=rJ=6tM3tFA@mail.gmail.com> <BY2PR0301MB06477C93FA8937F0ABD4393383D20@BY2PR0301MB0647.namprd03.prod.outlook.com>
Date: Fri, 5 Feb 2016 08:55:43 -0800
Message-ID: <CABp8EuLQD7iHp1XQYjreRotcMZaH=R2ZsJkPTsMSCSqTfMYegg@mail.gmail.com>
From: Benjamin Bangert <bbangert@mozilla.com>
To: Brian Raymor <Brian.Raymor@microsoft.com>
Content-Type: multipart/alternative; boundary=001a113d44d4d25f5e052b08b8cb
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/v-RRjuQkUQh0vGQH9QKJD3MZN8c>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Require the TTL header
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: Fri, 05 Feb 2016 16:55:48 -0000

On Thu, Feb 4, 2016 at 9:42 PM, Brian Raymor <Brian.Raymor@microsoft.com>
wrote:

>
> > Can we require a TTL value for web-push notifications?
>
> I'd support this requirement if it helps to enforce correct behavior in
> implementations.
>
> > Regarding the resource creation, the spec does not clearly state whether
> a Location header should be returned for a TTL of 0
> > since its intended that the message is only delivered to an online user.
> If so, it would be useful to mention.
>
> RFC7231 states:
>
> http://tools.ietf.org/html/rfc7231#section-4.3.3
>
>    If one or more resources has been created on the origin server as a
>    result of successfully processing a POST request, the origin server
>    SHOULD send a 201 (Created) response containing a Location header
>    field that provides an identifier for the primary resource created
>    (Section 7.1.2) and a representation that describes the status of the
>    request while referring to the new resource(s).
>

I took that to mean that no Location is returned if the user is offline
since no notification was created.


> > If it was a required header, we could return a 401 which would very
> quickly alert developers about the problem.
>
> Did you intend a 400 (Bad Request) rather than a 401 (Unauthorized)?


Yes, sorry, a 400 would be returned if it's missing.

v2.8.7 | Report a Bug | By Email