- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 3 Jul 2018 12:16:20 +1000
- To: Amos Jeffries <squid3@treenet.co.nz>
- Cc: ietf-http-wg@w3.org
Hi Amos, > On 2 Jul 2018, at 6:48 pm, Amos Jeffries <squid3@treenet.co.nz> wrote: > > But no, the rational for adding a new header does not make much sense > yet. There is already Forwarded header created for this same use-case > (amongst others) overlapping with Via. A new, single-purpose header is preferable, because CDNs need to bar customer configuration/manipulation/etc of the mechanism, and since Forwarded serves multiple purposes, that might be more difficult. > And why not push to get the problematic servers fixed instead of > polluting HTTP header space with more features everybody with middleware > has to support? Like this? https://trac.nginx.org/nginx/ticket/1362 Even if that were fixed tomorrow, there are a *lot* of deployed nginx servers that will behave this way for the foreseeable future, and AIUI other implementations who do similar things. As to "polluting" - the HTTP header name space is large, so I don't think that's a valid argument. Intermediaries aren't forced to implement this; again, a single CDN can get some benefit, since it can insert its token and then recognise it in incoming requests. Cheers, -- Mark Nottingham https://www.mnot.net/
Received on Tuesday, 3 July 2018 02:16:51 UTC