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

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.



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