Re: [whatwg/fetch] Cache-mode and upstream Cache-Control (#722)

Chrome's network stack has similar issues to those described by @wanderview in https://github.com/whatwg/fetch/issues/722#issuecomment-413559634. The code that adds the headers based on the flags is deep inside the network stack: https://cs.chromium.org/chromium/src/net/http/http_network_transaction.cc?type=cs&q=HttpNetworkTransaction::BuildRequestHeaders&g=0&l=1090.

I think it's easier for Chrome to add more headers to converge with other browsers than it is to remove headers, so from Chrome's point of view it would be better to retain steps 13 and 14.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/722#issuecomment-416845945