Re: H2 Implementation Debug State URI
Alcides Viamontes E <alcidesv@shimmercat.com> Thu, 28 July 2016 15:01 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9305212B042 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 28 Jul 2016 08:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.207
X-Spam-Level:
X-Spam-Status: No, score=-8.207 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=shimmercat-com.20150623.gappssmtp.com
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 OXpYvmm5Jlhu for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 28 Jul 2016 08:01:18 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9784D12D5D2 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 28 Jul 2016 08:01:18 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bSmjS-0007xY-Lv for ietf-http-wg-dist@listhub.w3.org; Thu, 28 Jul 2016 14:56:18 +0000
Resent-Date: Thu, 28 Jul 2016 14:56:18 +0000
Resent-Message-Id: <E1bSmjS-0007xY-Lv@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <alcidesv@zunzun.se>) id 1bSmjM-0007u9-Kx for ietf-http-wg@listhub.w3.org; Thu, 28 Jul 2016 14:56:12 +0000
Received: from mail-oi0-f53.google.com ([209.85.218.53]) by maggie.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <alcidesv@zunzun.se>) id 1bSmjK-0001cW-32 for ietf-http-wg@w3.org; Thu, 28 Jul 2016 14:56:12 +0000
Received: by mail-oi0-f53.google.com with SMTP id j185so66217578oih.0 for <ietf-http-wg@w3.org>; Thu, 28 Jul 2016 07:55:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shimmercat-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jKpvennfVeQjakIJrpIwp2VkT6vN4AQcNVEDA+osPm4=; b=LcAZyfW1OgmUzYXfZdUHCyx0mB+ZFNg+pRgTkwckGMzDGXA29+H/TEJVqdCxDRbVi6 D51cBv7HBIGOEPSWwZs9Xm5m2KdcRJq/n2wae4V2j2qLkm3tRN+VMh+pdubWEEpdi/xG cIup9uXhk0EQWJ/5EHe8F4rbU4cyQVDSsm+mJqPPLYy/cJdRl+dsZaTsxhYCDqNEQf8H 8eLL5X0EruUJV7qVZdG6jLt/7PLtnBiNCDks4q+txB26RUdPQnbXn7y6BosNJYiB16nF TTxoZS4AWblDn0Vpa6Bp4nqsbg1nlKqZ9Bn2VHnt5Oo+V0Ma3wybIY+NeyJs1393LiWy eR3g==
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:from:date :message-id:subject:to:cc; bh=jKpvennfVeQjakIJrpIwp2VkT6vN4AQcNVEDA+osPm4=; b=HTzQOSyFopehS6qFdiBv35zcU7hr4vctYQoGUh4jGQXdLb7zC6GIOXou035l9XqBNJ T9H+BLOvxP67FCIsXRiRiWD6T2vgaqV2o+Ov4BtV4zUu7ZjFkEe9a7MoTRv9qLzpei9h p8CmtirIBdNKctEaKT8aCEsf5l9L2i9I6mpAmMW0kK0ddpLRAc73T6/JrufVUmYO0qFH TE3X5PBy0wDoFoFZqOP7yxEmD87hlEoDPEXYavdAWxhVysace3WCfXEMLfNmEUXeqJhG fP4Rkn1RUuiLqA0eIawHqLSSQJRGV9CHF7ReXpWzGBVfu/14PvWt3rKoJ9XPsiNNaget uKtA==
X-Gm-Message-State: AEkoouugYHe98Ph5MiJJ3lS/daBaoAh4obpXAFfW8pGUl+wmjC0Mc5ysDzAwLTvOezx7B3PCuBlFYPNPUzUt3w==
X-Received: by 10.157.44.74 with SMTP id f68mr10901757otb.80.1469717743086; Thu, 28 Jul 2016 07:55:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.204.18 with HTTP; Thu, 28 Jul 2016 07:55:42 -0700 (PDT)
In-Reply-To: <3254E485-1719-4561-AA64-C003C81468A5@greenbytes.de>
References: <63CCB07A-0204-4CF7-B598-9497D7112021@lukasa.co.uk> <3254E485-1719-4561-AA64-C003C81468A5@greenbytes.de>
From: Alcides Viamontes E <alcidesv@shimmercat.com>
Date: Thu, 28 Jul 2016 16:55:42 +0200
Message-ID: <CAAMqGzbxSQaM7fMcku-YHb+T0uBZprYEvaeTwnN3vxvg9mXm4w@mail.gmail.com>
To: Stefan Eissing <stefan.eissing@greenbytes.de>
Cc: Cory Benfield <cory@lukasa.co.uk>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="94eb2c11f156ff49ed0538b3533d"
Received-SPF: pass client-ip=209.85.218.53; envelope-from=alcidesv@zunzun.se; helo=mail-oi0-f53.google.com
X-W3C-Hub-Spam-Status: No, score=-2.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_NW=0.5
X-W3C-Scan-Sig: maggie.w3.org 1bSmjK-0001cW-32 225c5f122d335a631d53b30702cf2e53
X-Original-To: ietf-http-wg@w3.org
Subject: Re: H2 Implementation Debug State URI
Archived-At: <http://www.w3.org/mid/CAAMqGzbxSQaM7fMcku-YHb+T0uBZprYEvaeTwnN3vxvg9mXm4w@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32073
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>
This is a nice debugging asset! But looking forward to a more generic mechanism that could be used leveraged by application servers and by web-applications, it could be possible to just leverage the "Forwarded" HTTP extension (RFC 7239). We do something like that for some bits and pieces : https://www.shimmercat.com/en/info/articles/forwarded-header/ On Thu, Jul 28, 2016 at 4:00 PM, Stefan Eissing < stefan.eissing@greenbytes.de> wrote: > Thanks, Cory!. Apache will offer this as a configurable handler and I will > make a beta available via github soon. Currently outputs lacks individual > streams and looks like this: > { > "settings": { > "SETTINGS_MAX_CONCURRENT_STREAMS": 100, > "SETTINGS_MAX_FRAME_SIZE": 16384, > "SETTINGS_INITIAL_WINDOW_SIZE": 65535, > "SETTINGS_ENABLE_PUSH": 1 > }, > "connFlowIn": 2147483647, > "connFlowOut": 12571993, > "sentGoAway": 0, > "in": { > "requests": 63, > "resets": 0, > "frames": 134, > "octets": 3831 > }, > "out": { > "responses": 62, > "frames": 130, > "octets": 13754 > }, > "push": { > "cacheDigest": "AQib_wA", > "promises": 1, > "submits": 1, > "resets": 0 > } > } > > -Stefan > > > Am 28.07.2016 um 14:38 schrieb Cory Benfield <cory@lukasa.co.uk>: > > > > All, > > > > During the HTTP workshop earlier this week, several HTTP/2 implementers > expressed a desire to extract information about the state of the H2 > connection from the perspective of their peer. This would be extremely > useful when developing, debugging, and testing implementations: given that > HTTP/2 is so highly stateful the vast majority of interoperability issues > come from implementations disagreeing about what the state of the > connection is (usually flow control windows!). > > > > Brad Fitzpatrick and I ended up prototyping a sample approach for > getting this information out of server implementations, based on issuing a > GET request to a specific well-known URI. This GET would return a JSON > document that contains various different pieces of information from inside > the implementation, such as window sizes and stream states. In addition, to > help debug flow control concerns, the response headers also include > information about flow control windows (because if a server believes it is > blocked behind flow control it can’t send the JSON document, but it can > send the response headers). Examples of this behaviour are available at > https://http2.golang.org/.well-known/h2interop/state and > https://shootout.lukasa.co.uk/.well-known/h2interop/state. > > > > The consensus amongst the implementers we spoke to were that this was a > good idea, and it would be good to collaborate on the information that > should be exposed here. For most HTTP/2 implementers one of the most > natural ways to collaborate on something like this is to use an Internet > Draft. For that reason, I have submitted the outline of a draft that > essentially defines what Brad and I have already done. You can find this > draft here: > https://tools.ietf.org/html/draft-benfield-http2-debug-state-00 > > > > I have no expectation that this will become a WG document. However, I’d > like to bring it to the attention of the working group to ensure that as > many implementers as possible can provide feedback on whether this kind of > approach is valuable or not, and what information they’d like made > available in this kind of mode. > > > > For anyone who wants to contribute, raise issues, or otherwise help with > the draft, it is hosted on GitHub: > https://github.com/python-hyper/draft-http2-debug-state. Issues and pull > requests are more than welcome, as is feedback on this list. > > > > Thanks, > > > > Cory > > > -- Alcides Viamontes E. Chief Executive Officer, Zunzun AB (+46) 722294542 (www.shimmercat.com is a property of Zunzun AB)
- Re: H2 Implementation Debug State URI Cory Benfield
- Re: H2 Implementation Debug State URI Alex Rousskov
- Re: H2 Implementation Debug State URI Poul-Henning Kamp
- RE: H2 Implementation Debug State URI Mike Bishop
- Re: H2 Implementation Debug State URI Alex Rousskov
- Re: H2 Implementation Debug State URI Cory Benfield
- Re: H2 Implementation Debug State URI Alex Rousskov
- Re: H2 Implementation Debug State URI Cory Benfield
- Re: H2 Implementation Debug State URI Alex Rousskov
- Re: H2 Implementation Debug State URI Cory Benfield
- Re: H2 Implementation Debug State URI Alex Rousskov
- Re: H2 Implementation Debug State URI Cory Benfield
- Re: H2 Implementation Debug State URI Stefan Eissing
- Re: H2 Implementation Debug State URI Martin Thomson
- Re: H2 Implementation Debug State URI Poul-Henning Kamp
- Re: H2 Implementation Debug State URI Cory Benfield
- Re: H2 Implementation Debug State URI Poul-Henning Kamp
- Re: H2 Implementation Debug State URI Alcides Viamontes E
- Re: H2 Implementation Debug State URI Stefan Eissing
- H2 Implementation Debug State URI Cory Benfield