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

alt-svc and proxies

From: Piotr Galecki <piotr_galecki@affirmednetworks.com>
Date: Mon, 4 Jan 2016 03:32:39 +0000
To: HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <2C515BE8694C6F4B9B6A578BCAC32E2F6D538FCC@MBX021-W3-CA-2.exch021.domain.local>
When reviewing the alt-svc draft it is not entirely clear to me from the draft how proxies should process Alt-Svc headers and
how they should behave when a response with the Alt-Svc header is received.
This should be defined.

IMO Alt-Svc header support should be required from proxies going forward.
Proxies should behave in the same/similar way as clients in respect to Alt-Svc headers.
They should cache information about alternative service available
and use the alt service for subsequent requests to origin.
Forward proxies supporting alternative services should also remove Alt-Svc headers
when forwarding a response to client.
This is because the protocol used for the client to proxy connection is defined (by user or WPAD) in proxy configuration settings
and it should not be modified by the alternative service header.

I'd like to propose the following changes:

- change "client" to "client (or intermediary)" in the text throughout the draft wherever appropriate

- possibly to section 2.4 or other add text:
  "Intermediaries when receiving a response with Alt-Svc header SHOULD cache the availability of the alternative service
   and use the alt service when forwarding subsequent requests to the origin,  provided the alternative service information is fresh.
   In order to continue using the user (or WPAD) configured protocol for the client to proxy connection
   forward proxies supporting alternative services SHOULD remove Alt-Svc header when forwarding a response to client."
Received on Monday, 4 January 2016 03:33:09 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:10 UTC