7 ms·
1. H2 2018 2. Relies on a "web standard" that Google is pushing and is implementing in Chrome (and so far, I think, only confirmed to be in Chrome)
by thedz 9y ago
1. H2 2018
2. Relies on a "web standard" that Google is pushing and is implementing in Chrome (and so far, I think, only confirmed to be in Chrome)
- deleted 9y ago[deleted]
- jyasskin 9y agoWe're expecting to follow roughly the same path that SPDY (eventually HTTP/2) took: iterate on some early versions in Chrome to get experience while the format goes through the standardization process, and eventually remove those in favor of the standardized version. You can follow the IETF part of the process at https://tools.ietf.org/html/draft-yasskin-http-origin-signed-responses-01 https://tools.ietf.org/html/draft-yasskin-http-origin-signed....