[whatwg/fetch] Should the reload-navigation flag behave similarly to the "reload" cache mode? (Issue #1899)

trflynn89 created an issue (whatwg/fetch#1899)

### What is the issue with the Fetch Standard?

In the HTML spec, we are instructed to set the fetch request's reload-navigation flag during document reloads:

https://html.spec.whatwg.org/multipage/browsing-the-web.html#create-navigation-params-by-fetching
> 7. If entry's document state's reload pending is true, then set request's reload-navigation flag.

This flag is ultimately only ever used in the fetch spec for the [isReloadNavigation](https://fetch.spec.whatwg.org/#dom-request-isreloadnavigation) attribute.

Should this flag also affect interaction with the cache, in the same way that the [cache mode](https://fetch.spec.whatwg.org/#concept-request-cache-mode) does? That is, the HTTP cache is not checked:

https://fetch.spec.whatwg.org/#http-network-or-cache-fetch
> 25. If httpRequest’s cache mode is neither "no-store" nor "reload", then:
    1. Set storedResponse to the result of selecting a response from the httpCache, possibly needing validation, as per the "Constructing Responses from Caches" chapter of HTTP Caching, if any.

The use case we're working through in Ladybird here is when the user explicitly refreshes a page. Both Firefox and Chrome will send a conditional request for the document URL for user-initiated reloads (i.e. they attach an If-Modified-Since request header). Chrome will additionally attach a `Cache-Control: max-age=0` request header.



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

Message ID: <whatwg/fetch/issues/1899@github.com>