Allow servers to specify max-age in the client hints header about netinfo HOT 2 CLOSED

This is basically defining a separate cache from the HTTP cache, which has significant implementation overhead, and it appears you're scoping it to the entire origin, rather than just the response. These things are possible, but it's a pretty big change.

My understanding was that the common use case for client hints is for subresources, where having Accept-CH for the initial page load doesn't matter; i.e., you get Accept-CH on the HTML load, and then send the various hints on the subresource requests. What's your use case here?

P.S. Accept-CH is being defined over at https://github.com/httpwg/http-extensions, so if you want to extend it, you should really discuss it over there.

from netinfo.

@mnot Thanks!. I have filed httpwg/http-extensions#306, so I am going to close this bug. We can continue the discussion there, but I was under the impression that hints were not explicitly restricted to subresources, and browsers could include hints on the next HTML (aka main frame / navigation) requests too.

The real use case here is that content providers are interested in receiving hints on the HTML (aka main frame) requests so they can accordingly adapt the content of the HTML (e.g., URLs of subresources).

from netinfo.