Re: Understanding application/http
Amos Jeffries <squid3@treenet.co.nz> Mon, 25 March 2024 05:23 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=ietf.org@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 D2A3FC14F71C for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 24 Mar 2024 22:23:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.757
X-Spam-Level:
X-Spam-Status: No, score=-7.757 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=w3.org header.b="E03Kar8s"; dkim=pass (2048-bit key) header.d=w3.org header.b="Y5LDmO/4"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p41t-JLx4q5b for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 24 Mar 2024 22:23:38 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F4D4C14F71D for <httpbisa-archive-bis2Juki@ietf.org>; Sun, 24 Mar 2024 22:23:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Subject:Content-Type:In-Reply-To:From:References:To:MIME-Version:Date :Message-ID:Cc:Reply-To; bh=YzFeCjkK81j19YSCtgsI6Vd9zxbhkDgho+HQqwZxkgM=; b=E 03Kar8sPPGhFJjgusiEkJ1QtBHRWBLCcPP8TZ4erlgElNkknQ316aqwWgo1cYZ6Yraq/PkogAkfL+ BDkYp+Xv3eYNKQecPKnBV4dQjLfoPCUvDZu4X0VZ7vxA5XDG9aY8qADxNH8n7lcdYqLUTAzPSs0dx +lombzNce56jUC8ea7UNVW3eTO92KJwWzj7Rp8NvftFAbwDuMzNhE2YFAuOzYrO71sShGpMAplnGq ouJRFTLgOurcfiikzrShiwoRdD/S+aV3nz4nGq3J2DMeEBG+sqZUZpI89HsPqOOCxMDyO+fneUkxH npAswg9BV6wm+jrtphGkG4a+pc8Fi1xMw==;
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1rocmC-00FYUx-5Z for ietf-http-wg-dist@listhub.w3.org; Mon, 25 Mar 2024 05:21:40 +0000
Resent-Date: Mon, 25 Mar 2024 05:21:40 +0000
Resent-Message-Id: <E1rocmC-00FYUx-5Z@lyra.w3.org>
Received: from puck.w3.org ([34.196.82.207]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <squid3@treenet.co.nz>) id 1rocm9-00FYTw-Lr for ietf-http-wg@listhub.w3.org; Mon, 25 Mar 2024 05:21:37 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Content-Type:In-Reply-To:From:References:To:Subject:MIME-Version:Date :Message-ID:Cc:Reply-To; bh=YzFeCjkK81j19YSCtgsI6Vd9zxbhkDgho+HQqwZxkgM=; t=1711344097; x=1712208097; b=Y5LDmO/4EIfpotzD8PAg8zVWQBM2M7VHlFgi4mz3oxf0cBd Nv68U2ljqMRxTV+mPqxdJjgkqjBFPyFEARQJrandqP0vQVlVsEQy/QkHYIhOatlHuehdwspPX4KCf 0OcYJe0Y7DXnmHcl9T4nPVx1YFXjw1O3ej9kKnTuhhUcKxep8oqYhNE3gEEFG62yu0aaR+R4fWxYe LpXmBbN2yt4Ws2fhSJaOoIvSVxW3VTq30kw/a/+CjqjzMYhmAK3pg0KwGNjtuuIlAAYh7i/etwlA2 3KWYXeiW3pHLTGkRFlH/PNEp2qlSvenOlM4eBqhZgqUHyulzfwB90/41dZbI4mxg==;
Received-SPF: pass (puck.w3.org: domain of treenet.co.nz designates 203.94.33.146 as permitted sender) client-ip=203.94.33.146; envelope-from=squid3@treenet.co.nz; helo=treenet.co.nz;
Received: from [203.94.33.146] (helo=treenet.co.nz) by puck.w3.org with esmtp (Exim 4.96) (envelope-from <squid3@treenet.co.nz>) id 1rocm7-00BWqy-0d for ietf-http-wg@w3.org; Mon, 25 Mar 2024 05:21:37 +0000
Received: from [192.168.1.7] (unknown [114.23.221.183]) by treenet.co.nz (Postfix) with ESMTPA id 4B8D3300036 for <ietf-http-wg@w3.org>; Mon, 25 Mar 2024 18:21:30 +1300 (NZDT)
Message-ID: <a4060fba-c82f-4050-b3e1-a4a20b77f07e@treenet.co.nz>
Date: Mon, 25 Mar 2024 18:21:28 +1300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: ietf-http-wg@w3.org
References: <XN4p0_W6GSjdZDKQR_0wMBYAfdbXM0k20Rxx2965ObN1N6FMlTUGxQUoHnevdjM4jKHkS_B2P99RXu5UlgqYjxnUUk1ZsQg3JBGnhu_7LkQ=@protonmail.com>
From: Amos Jeffries <squid3@treenet.co.nz>
In-Reply-To: <XN4p0_W6GSjdZDKQR_0wMBYAfdbXM0k20Rxx2965ObN1N6FMlTUGxQUoHnevdjM4jKHkS_B2P99RXu5UlgqYjxnUUk1ZsQg3JBGnhu_7LkQ=@protonmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-W3C-Hub-Spam-Status: No, score=-4.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DMARC_MISSING=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: puck.w3.org 1rocm7-00BWqy-0d b305336dab8e6c7bd5b1d86ee18413d8
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Understanding application/http
Archived-At: <https://www.w3.org/mid/a4060fba-c82f-4050-b3e1-a4a20b77f07e@treenet.co.nz>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/51906
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: <https://www.w3.org/email/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
On 19/03/24 01:41, Rahul Gupta wrote: > Hi, > > This is a question that I have been looking to understand for some time, and I am hoping that since this is IETF week, someone might indulge me! > > Where does the media-type `application/http` in RFC9112 come from? FWIW, the media type(s) for HTTP have been around since at least the beginning of HTTP/1.0. I'm not sure myself where or why they were created. Maybe on of the OG will remember. > Where is it used? These days, in protocols which wrap whole HTTP messages to transmit them - such as <https://www.rfc-editor.org/rfc/rfc8188.html>. > And are there any examples of its use in the wild? > VPN and CDN systems are the most likely place to find it. Though I cannot point at any particular ones. HTH Amos
- Understanding application/http Rahul Gupta
- Re: Understanding application/http Amos Jeffries
- RE: Understanding application/http Pavlo