For the record, the Accept header in Chrome for navigation requests (which will be available to a push-enabled server) **does** contain the supported image formats as well: ``` GET /w3ctag/design-reviews/issues/202 HTTP/1.1 Host: github.com User-Agent: .. Chrome/61.0.3163.100 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8 ``` I don't know if that is standardised and intended to be used for this purpose, but it is one possible way to inform servers of supported formats of sub resources. For the case of other non-image files (such as fonts) this wouldn't suffice right now. For fonts, preload has a `type` attribute, where generally only the "best" format is requested, but while that solves the issue for preload, it does not solve it for push. What is the intended strategy there? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/202#issuecomment-332903331
Received on Thursday, 28 September 2017 17:15:25 UTC