- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 29 Jan 2015 17:41:08 +0100
- To: Mark Nottingham <mnot@mnot.net>, Erik Nygren <erik@nygren.org>
- CC: HTTP Working Group <ietf-http-wg@w3.org>
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
Received on Thursday, 29 January 2015 16:41:53 UTC