IETF Logo Mail Archive

Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME

Lucas Pardue <lucaspardue.24.7@gmail.com> Wed, 07 August 2019 00:02 UTC

Return-Path: <lucaspardue.24.7@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E48B12008B for <quic@ietfa.amsl.com>; Tue, 6 Aug 2019 17:02:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 L0iz6kQA1xJv for <quic@ietfa.amsl.com>; Tue, 6 Aug 2019 17:02:55 -0700 (PDT)
Received: from mail-ua1-x92e.google.com (mail-ua1-x92e.google.com [IPv6:2607:f8b0:4864:20::92e]) (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 BB76612009C for <quic@ietf.org>; Tue, 6 Aug 2019 17:02:55 -0700 (PDT)
Received: by mail-ua1-x92e.google.com with SMTP id v20so34371677uao.3 for <quic@ietf.org>; Tue, 06 Aug 2019 17:02:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=0My8kAJwvlP8IHn/Mrx8r1zXOn0HNOA8lD2DXHTcEew=; b=iV47rxKz35rKqvw+FS6y2h2igH77f7MjU9UDBQmJixlY8k0ifopUlCMD69S+OnzaHS c4/MY6IB2s6By4QT8fW8Acpnieb/mAwNb2Nz06unwGixaJw+ZYV4fOdlwo3xc44Nf1tX nPqnzogqVEXSlf9stVHazW3s4MO8ft0IyvSJ5nm7Ga7hUBafU77c35eJG5s5/7kxMjba OGVg1HSE3v4XnxfZiLzKiSn+/N71QAFRGwPBt3jhaf6eYUbz7kGZ1XfIvvsWxVu4LCzP +So+5dPYRJcTkkl6R9IqFI4hu5iF1DVNep+uKGX8MLIdiryVfgG7ghuNp4WFy6xin8ly MfNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=0My8kAJwvlP8IHn/Mrx8r1zXOn0HNOA8lD2DXHTcEew=; b=Rh+V2KxF/93CvYvCxt8La+GGrUZGmVU4y1a4ZFBrp4rY+kj8o5A9LyXcFSHXRwITRT f5cWUD4SbJdXO5nYbMhLK7zjFr2gnQ9+y8pvkwEO9CpU/BmkI77RKaBhK41tAGbkOp+Y h/+y2gD63H/ZYheJN34J/0DL4vYU9HNMRc7ffJDHZsGgRgu0F2i/PCISUMmx/2hQfYrc N6zQ5FMbhdht23mFiNftvgFJMEUBnza+LobcFgoDyY9uFF+n4cALtjePAzAYtOews8UC tpgZtVvJ9o/KzEytAim2zuiM0NCOxJapP4nFtyvbwSHC/XZs0jwiky6++XxVMBHMRXrk 3ksA==
X-Gm-Message-State: APjAAAX/ZYpNCkR+4uEeoftPl7b75jRtyt61/hEl5psnb8FIGv7LxITH JNHzt+xprfN8oMz9+gYOadGUQs5jyqIxK+reo8yaSQjX
X-Google-Smtp-Source: APXvYqxAPm1q4DdLQYo5tIMXtk0vQhHGVPrCy0sBnz4Kt8CqZ22CRW761ndi+zQX8xSH3Gn1xjxNWEQ8g8MXzYevaW4=
X-Received: by 2002:ab0:7491:: with SMTP id n17mr3882936uap.102.1565136174650; Tue, 06 Aug 2019 17:02:54 -0700 (PDT)
MIME-Version: 1.0
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 07 Aug 2019 01:02:55 +0100
Message-ID: <CALGR9ob7=MzO5qt987dpBAxBqnsMRvkrgYz7svktKsMNNhjAdw@mail.gmail.com>
Subject: Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b71a2b058f7ba94c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/G0PbDDh6rRtRvA7k4v6rL-KebMg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2019 00:02:57 -0000

Hello WG,

As part of the HTTP error analysis and feedback, in June I created issue
#2809 "Rationalise HTTP_WRONG_STREAM and HTTP_UNEXPECTED_FRAME" [1].

In short, HTTP_WRONG_STREAM is used for connection errors when a
non-allowed frame is received by a peer (e.g a server receiving
PUSH_PROMISE), or when a request sequence is malformed.
HTTP_UNEXPECTED_FRAME is used for connection errors when an allowed frame
is received on the wrong type of stream (e.g. a client receiving
PUSH_PROMISE on the control stream).

Issue 2809 suggests combining these error codes but I've yet to make a PR.
In the meantime, a fair amount of error code refactoring has taken place
and I'm not sure how much demand there is for the change.

If you have an opinion on this I'd appreciate feedback here or on the
ticket.

Cheers
Lucas

[1] https://github.com/quicwg/base-drafts/issues/2809

v2.23.0 | Report a Bug | By Email