Re: negotiated protocol in Navigation and Resource Timing

On Fri, Oct 17, 2014 at 5:49 PM, Ilya Grigorik <igrigorik@google.com> wrote:
> We need protocol info in Navigation Timing because there is no way to get
> the Response object for the navigation. That said, I would also like to see
> it on Resource Timing: developer convenience, consistent API interface.

What exactly is "protocol info"?


> Also, right now we're working on the assumption that Fetch's Response object
> could/should expose the protocol.
>
> Anne: any thoughts on the latter?

It exposes the protocol insofar that it exposes the scheme  through
the response's url.


(It wasn't clear to me we wanted to expose the response of an <img> as
well by the way. I thought we just wanted to control the request for
it. It seems doable, although e.g. <img> can represent many requests
and many responses so we likely cannot have a generic solution.)


-- 
https://annevankesteren.nl/

Received on Saturday, 18 October 2014 09:18:22 UTC