IETF Logo Mail Archive

Re: [Webpush] Provide a method to indicate rate-limit issues

Brian Raymor <Brian.Raymor@microsoft.com> Sat, 31 October 2015 22:04 UTC

Return-Path: <Brian.Raymor@microsoft.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 41A271B3BC7 for <webpush@ietfa.amsl.com>; Sat, 31 Oct 2015 15:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 WR1vI0LEsJzy for <webpush@ietfa.amsl.com>; Sat, 31 Oct 2015 15:04:56 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0147.outbound.protection.outlook.com [207.46.100.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E4F71B3BC5 for <webpush@ietf.org>; Sat, 31 Oct 2015 15:04:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=eZPJZNeZuKZ6CO09i7ob1QlkcJ36lyL/ZKWo3Fs1F4w=; b=UMCxAdzA1knMcCacIb7nHLW/X/Da/hViWzyu7QRE2OOO/Xqz3/1smylvF90f2l41VerToWliOErElAk2ve9sNpBSBxeXrWf5Zmp1O0vLr/zaXGwKahavNA6kBi1hTqc+C3AA+nIEcfit9nvrAJ2Fc8s5JpLGA+B4unvsRizzA0Y=
Received: from BY2PR0301MB0647.namprd03.prod.outlook.com (10.160.63.14) by BY2PR0301MB0647.namprd03.prod.outlook.com (10.160.63.14) with Microsoft SMTP Server (TLS) id 15.1.312.18; Sat, 31 Oct 2015 22:04:55 +0000
Received: from BY2PR0301MB0647.namprd03.prod.outlook.com ([10.160.63.14]) by BY2PR0301MB0647.namprd03.prod.outlook.com ([10.160.63.14]) with mapi id 15.01.0312.014; Sat, 31 Oct 2015 22:04:55 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Benjamin Bangert <bbangert@mozilla.com>, "webpush@ietf.org" <webpush@ietf.org>
Thread-Topic: [Webpush] Provide a method to indicate rate-limit issues
Thread-Index: AQHRE0iQWJvjfricNEGNDNBvA190dJ6GJLgA
Date: Sat, 31 Oct 2015 22:04:54 +0000
Message-ID: <BY2PR0301MB06474751D2491959EE53ABFE832E0@BY2PR0301MB0647.namprd03.prod.outlook.com>
References: <CABp8EuKLJQQbyPCbRTTq=ZxYaQaMCQPYe+FUveUs=3tGF4MHpg@mail.gmail.com>
In-Reply-To: <CABp8EuKLJQQbyPCbRTTq=ZxYaQaMCQPYe+FUveUs=3tGF4MHpg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Brian.Raymor@microsoft.com;
x-originating-ip: [122.210.83.163]
x-microsoft-exchange-diagnostics: 1; BY2PR0301MB0647; 5:B+k4/iP681wWBluy8U5pVo/5PX/xWT53YoqnQUnFAw12r7vOkZSNu9bVHN3CxuhtO0O84OzeMQwDxLFj9Wr0EokqeAjErvpRv4erw9gDJo7UDnIHzgkRkFZb1CdVhmvL+L0EPMkGE+n2fG6AXhU8jA==; 24:sU5ImGoo+9l7at7ZaKfvl5YmozHctTz/uYT9RS5/50I1CnziOgHWdYQyyk3Iw6vGVI4WIDgXJ032Ie8UV6/PN5N6iNtxP0R2blRew7OK9rg=; 20:JKeHVvAILYBF4/14ceNoTNkDmbhzPLIwRsNZSn6Agqf886zQU+jMY+SSCwka3DZyHOBDcFAo0+6maHqEHONGyg==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0301MB0647;
x-microsoft-antispam-prvs: <BY2PR0301MB0647039011072B5846C79D28832E0@BY2PR0301MB0647.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425024)(601004)(2401047)(8121501046)(5005006)(520078)(3002001)(10201501046)(61426024)(61427024); SRVR:BY2PR0301MB0647; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0301MB0647;
x-forefront-prvs: 07467C4D33
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(199003)(189002)(377454003)(5002640100001)(50986999)(5003600100002)(76176999)(105586002)(8990500004)(10090500001)(10290500002)(106116001)(106356001)(15975445007)(107886002)(101416001)(99286002)(5001960100002)(97736004)(54356999)(5001770100001)(92566002)(2501003)(77096005)(2950100001)(76576001)(2900100001)(102836002)(81156007)(561944003)(19580405001)(11100500001)(5007970100001)(189998001)(5008740100001)(5004730100002)(19580395003)(66066001)(33656002)(86362001)(74316001)(122556002)(5005710100001)(10400500002)(86612001)(40100003)(87936001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0301MB0647; H:BY2PR0301MB0647.namprd03.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2015 22:04:54.7557 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0301MB0647
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/wmThxQ0-Vlp6_hiBtZCyLcP-t-I>
Subject: Re: [Webpush] Provide a method to indicate rate-limit issues
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: Sat, 31 Oct 2015 22:04:58 -0000

On October 31 2015 at 4:24 AM, Benjamin Bangert <bbangert@mozilla.com> wrote:

> It would be nice to have a uniform way to indicate to an Application Server that its being rate-limited
> and it should back-off on its sending, in a separate way than using a 503. 503's are used for a variety
> of issues, separate from rate-limiting, perhaps a different status code, and/or a header indicating
> when the app-server should resume.

The earlier proposal from JR - http://www.ietf.org/mail-archive/web/webpush/current/msg00308.html - was to include a reference to 429 with Retry-Header:

https://tools.ietf.org/html/rfc6585

   The 429 status code indicates that the user has sent too many
   requests in a given amount of time ("rate limiting").

   The response representations SHOULD include details explaining the
   condition, and MAY include a Retry-After header indicating how long
   to wait before making a new request.

   For example:

   HTTP/1.1 429 Too Many Requests
   Content-Type: text/html
   Retry-After: 3600

Would this address your requirements? 

...Brian

v2.23.0 | Report a Bug | By Email