Re: HTTP2 Stream timeouts?
Martin Thomson <martin.thomson@gmail.com> Thu, 07 August 2014 17:33 UTC
Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 061FE1A006C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 7 Aug 2014 10:33:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.003
X-Spam-Level:
X-Spam-Status: No, score=-7.003 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_HI=-5, RP_MATCHES_RCVD=-0.001, 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 z9aaul42NHcs for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 7 Aug 2014 10:33:21 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 774311A00A3 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 7 Aug 2014 10:32:57 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XFRVW-0005e5-Mo for ietf-http-wg-dist@listhub.w3.org; Thu, 07 Aug 2014 17:29:42 +0000
Resent-Date: Thu, 07 Aug 2014 17:29:42 +0000
Resent-Message-Id: <E1XFRVW-0005e5-Mo@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1XFRV5-0005cy-5p for ietf-http-wg@listhub.w3.org; Thu, 07 Aug 2014 17:29:15 +0000
Received: from mail-wi0-f180.google.com ([209.85.212.180]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1XFRV4-0007Uf-9E for ietf-http-wg@w3.org; Thu, 07 Aug 2014 17:29:15 +0000
Received: by mail-wi0-f180.google.com with SMTP id n3so5370579wiv.1 for <ietf-http-wg@w3.org>; Thu, 07 Aug 2014 10:28:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=y18J9bhJICyKJj3W8MfjbkUdOdvML4BMfSg/hH4UdNw=; b=sFXU+Llc9+I3b4ul4pEZYFyMumVYN5yNxJQOBK6lqlIm7yCo49uPnI4TksMR9+OU7u 2pS4rIDQJhACIcoejwhPYqxEwkYum/EbvdYRbaJX7WlCSqVgka3anJt3bQV/kOGkAOJi rsrrgeFfU0ix+GS+egsErRGLQjpNrx2Nb2FOnPlNrU6QoQWeNOvtAIFIBS161Dfrf8QQ C2sqN+Pi4bWJvVCab46lkGCfGkyHTR/WS2fGgYHc7BABohUnJMxcDSXkIy2mW/FhXmDf kxDusGldqdSB/lhTb27ZzE00QhymR8GCZZuMr2MYl2pCHkknR6z6u9Z69lvkG0dc2p7g ZP7Q==
MIME-Version: 1.0
X-Received: by 10.194.91.228 with SMTP id ch4mr25911966wjb.59.1407432527937; Thu, 07 Aug 2014 10:28:47 -0700 (PDT)
Received: by 10.194.6.229 with HTTP; Thu, 7 Aug 2014 10:28:47 -0700 (PDT)
In-Reply-To: <CAH_y2NEk+uYisQBh0Ox_FSe1kzXFSj7X75akr2dzgnn+4wjeqw@mail.gmail.com>
References: <CAH_y2NEk+uYisQBh0Ox_FSe1kzXFSj7X75akr2dzgnn+4wjeqw@mail.gmail.com>
Date: Thu, 07 Aug 2014 10:28:47 -0700
Message-ID: <CABkgnnW4SRGCMUQceNn0SuBLotjdxQXiBbdAVcEfqbHBVm45ow@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Greg Wilkins <gregw@intalio.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.212.180; envelope-from=martin.thomson@gmail.com; helo=mail-wi0-f180.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.733, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1XFRV4-0007Uf-9E 96c84f2cd8a2c7b92c58f29ab6e55269
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP2 Stream timeouts?
Archived-At: <http://www.w3.org/mid/CABkgnnW4SRGCMUQceNn0SuBLotjdxQXiBbdAVcEfqbHBVm45ow@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/26556
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On 6 August 2014 23:01, Greg Wilkins <gregw@intalio.com> wrote: > Note that I can see at least one use-case for long held idle stream. > Basically it is the long polling use-case of "protocol abuse". Frameworks > will still long poll over http2 and would benefit from a bit more certainty > over how long an idle stream can be expected to live. I can even imaging > more creative protocol abuse where a long held stream is used to enable push > promises to be sent, thus allowing arbitrary resources to be sent from > server to client. No way anyone would do that... https://tools.ietf.org/html/draft-thomson-webpush-http2-00
- HTTP2 Stream timeouts? Greg Wilkins
- Re: HTTP2 Stream timeouts? Martin Thomson
- Re: HTTP2 Stream timeouts? Michael Sweet
- Re: HTTP2 Stream timeouts? Greg Wilkins