W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2015

Re: #34: Alt-Svc-Used indicator granularity

From: Mark Nottingham <mnot@mnot.net>
Date: Fri, 30 Jan 2015 15:49:12 +1100
Cc: Erik Nygren <erik@nygren.org>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <257CCD00-DF7D-4197-891C-6D37BBA23FD0@mnot.net>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
Think so...

> On 30 Jan 2015, at 3:41 am, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 2015-01-28 00:09, Mark Nottingham wrote:
>> Thanks, Erik.
>> 
>> Does anyone else have comment / concern here?
>> 
>> Cheers,
> 
> OK, so we're going back to <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-alt-svc-01.html#service>:
> 
>> 4. The Service HTTP Header Field
>> 
>> The Service HTTP header field is used in requests to indicate the identity of the alternate service in use, just as the Host header field identifies the host and port of the origin.
>> 
>> Service = uri-host [ ":" port ]
>> 
>> Service is intended to allow alternate services to detect loops, differentiate traffic for purposes of load balancing, and generally to ensure that it is possible to identify the intended destination of traffic, since introducing this information after a protocol is in use has proven to be problematic.
>> 
>> When using an Alternate Service, clients MUST include a Service header in all requests.
>> 
>> For example:
>> 
>> GET /thing
>> Host: origin.example.com
>> Service: alternate.example.net
>> User-Agent: Example/1.0
> 
> ...except the header field name stays "Alt-Used", and the MUST becomes a SHOULD?
> 
> Will we still need the extension parameters?
> 
> Best regards, Julian
> 

--
Mark Nottingham   https://www.mnot.net/
Received on Friday, 30 January 2015 04:49:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:42 UTC