Re: updated http 1.1 rfcs and hop-by-hop from Martijn Faassen on 2014-08-19 (ietf-http-wg@w3.org from July to September 2014)

From: Martijn Faassen <faassen@startifact.com>
Date: Tue, 19 Aug 2014 10:35:49 +0200
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: ietf-http-wg@w3.org
Message-ID: <CAGT4ZFjz52EesnhE9g4d-B4-XRKgioMaHetXOpyeBtgstpDHsQ@mail.gmail.com>

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

Received on Tuesday, 19 August 2014 08:36:16 UTC