{"action":"opened","issue":{"url":"https://api.github.com/repos/w3c/resource-timing/issues/61","repository_url":"https://api.github.com/repos/w3c/resource-timing","labels_url":"https://api.github.com/repos/w3c/resource-timing/issues/61/labels{/name}","comments_url":"https://api.github.com/repos/w3c/resource-timing/issues/61/comments","events_url":"https://api.github.com/repos/w3c/resource-timing/issues/61/events","html_url":"https://github.com/w3c/resource-timing/issues/61","id":162907515,"number":61,"title":"transferSize and TAO redirects","user":{"login":"yoavweiss","id":786187,"avatar_url":"https://avatars.githubusercontent.com/u/786187?v=3","gravatar_id":"","url":"https://api.github.com/users/yoavweiss","html_url":"https://github.com/yoavweiss","followers_url":"https://api.github.com/users/yoavweiss/followers","following_url":"https://api.github.com/users/yoavweiss/following{/other_user}","gists_url":"https://api.github.com/users/yoavweiss/gists{/gist_id}","starred_url":"https://api.github.com/users/yoavweiss/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/yoavweiss/subscriptions","organizations_url":"https://api.github.com/users/yoavweiss/orgs","repos_url":"https://api.github.com/users/yoavweiss/repos","events_url":"https://api.github.com/users/yoavweiss/events{/privacy}","received_events_url":"https://api.github.com/users/yoavweiss/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-06-29T11:58:55Z","updated_at":"2016-06-29T11:58:55Z","closed_at":null,"body":"A couple of weird things spotted while reviewing Blink's implementation docs:\r\n\r\n> the size, in octets received from a HTTP-network fetch, consumed by the response header fields and the response payload body [RFC7230] if the last non-redirected fetch of the resource passes the timing allow check algorithm.\r\n\r\n\"last\" here seems spurious and confusing. If we have a redirection chain, we can expose the size if the final resource fetch passes TAO checks. Unless I'm missing some weird scenario, that would be the first, last and only non-redirected fetch in that chain.\r\n\r\n> If there are HTTP redirects or equivalent when navigating and if all the redirects or equivalent are from the same origin [RFC6454], this attribute should include the HTTP overhead of incurred redirects\r\n\r\nIs there a particular reason we don't expose the redirection overhead of TAO-enabled redirects? I think we should, unless some security considerations dictate otherwise."}}
{"actor":{"display_login":"yoavweiss"}}