IETF Logo Mail Archive

Re: updated http 1.1 rfcs and hop-by-hop

Martijn Faassen <faassen@startifact.com> Tue, 19 August 2014 08:39 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 B6D1E1A8858 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Aug 2014 01:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.948
X-Spam-Level:
X-Spam-Status: No, score=-6.948 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, 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 pvzSllAdgKa2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Aug 2014 01:39:32 -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 6A3381A8857 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 19 Aug 2014 01:39:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XJeuM-0002CY-Ha for ietf-http-wg-dist@listhub.w3.org; Tue, 19 Aug 2014 08:36:46 +0000
Resent-Date: Tue, 19 Aug 2014 08:36:46 +0000
Resent-Message-Id: <E1XJeuM-0002CY-Ha@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <martijn.faassen@gmail.com>) id 1XJets-00027i-Ck for ietf-http-wg@listhub.w3.org; Tue, 19 Aug 2014 08:36:16 +0000
Received: from mail-oi0-f50.google.com ([209.85.218.50]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martijn.faassen@gmail.com>) id 1XJetr-0000yN-5x for ietf-http-wg@w3.org; Tue, 19 Aug 2014 08:36:16 +0000
Received: by mail-oi0-f50.google.com with SMTP id a141so4366152oig.23 for <ietf-http-wg@w3.org>; Tue, 19 Aug 2014 01:35:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HRis2lO3Dl4Xfmq//1eTP98oPm2Vbf8OhmhD5SiDpWw=; b=CDvaLBXhLamscapPn7E4U4JiPKHCnBELCn+Kk6ZUj9jWU3y2g24SmxqybYD2JQaMLt r+qI5sWnGVYjGxEz5KIqWhVITo7lcHGwN6hb8JuOuNJtg4zJP/4w7k0DbFajgJ//ZX+p /3V6LxpcYfYRfKPpFYbjb4VSW4D5d99QxpQuzic1sYSswb0/prPj2Eznrti+LjQjxCFI bA4vbS/k3tiKPPBGffC4zzBBfjaJU/pTVLQ+k+4hWd/+DrEwWViLd9RUSKzel/tpG7DK p03eiUsPsfSWkSnnX9JgsZcLOX/XDrx37WubujkkJVKYtDZemTQinPAWrJ84m1F8vKBw Ql7g==
MIME-Version: 1.0
X-Received: by 10.60.174.3 with SMTP id bo3mr41439935oec.31.1408437349198; Tue, 19 Aug 2014 01:35:49 -0700 (PDT)
Sender: martijn.faassen@gmail.com
Received: by 10.182.106.99 with HTTP; Tue, 19 Aug 2014 01:35:49 -0700 (PDT)
In-Reply-To: <53F2E29D.7070506@treenet.co.nz>
References: <CAGT4ZFhOmN6N9zT0Z=edx6_kMUPczOc4zVNjQzDk5Bw3DFjtww@mail.gmail.com> <CAGT4ZFjt__Ct2n06gWJ5A2yLU0ZjTkSR19JG02PJ0W4SzRr=nQ@mail.gmail.com> <53F2E29D.7070506@treenet.co.nz>
Date: Tue, 19 Aug 2014 10:35:49 +0200
X-Google-Sender-Auth: EnKV5c1C9kTo_IXZv5lKcJlJJEc
Message-ID: <CAGT4ZFjz52EesnhE9g4d-B4-XRKgioMaHetXOpyeBtgstpDHsQ@mail.gmail.com>
From: Martijn Faassen <faassen@startifact.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: ietf-http-wg@w3.org
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.218.50; envelope-from=martijn.faassen@gmail.com; helo=mail-oi0-f50.google.com
X-W3C-Hub-Spam-Status: No, score=-2.6
X-W3C-Hub-Spam-Report: AWL=-1.934, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1XJetr-0000yN-5x 6e0b1c7cc23d7b448e8b1ca4453141a4
X-Original-To: ietf-http-wg@w3.org
Subject: Re: updated http 1.1 rfcs and hop-by-hop
Archived-At: <http://www.w3.org/mid/CAGT4ZFjz52EesnhE9g4d-B4-XRKgioMaHetXOpyeBtgstpDHsQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/26649
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>

Hi there,

I'm not sure I'm getting it yet. Does this mean that servers should be
sending out a Connection header that looks
like this?

Connection: close, Transfer-Encoding

Instead of just:

Connection: close

Or is 'Transfer-Encoding' a hopX-by-hopY behavior (I don't understand
what this is)?

I'm having trouble finding where the RFC currently specifies that a
particular header, such as Transfer-Encoding, should be in a
'Connection' entry.

Regards,

Martijn

v2.23.0 | Report a Bug | By Email