{cache: "no-cache"} vs Cache-Control: immutable

Open
#308 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
html
Domain
api, web-dev

Research direction

Read the Fetch Standard's cache-handling rules and the linked immutable proposal first. Determine whether fetch(aURLWithImmutableCache, {cache: "no-cache"}) should make a conditional request or use the cached response directly; done means the standard resolves this conflict and documents the chosen behavior.

Written by the indexing model from the issue text.

Description

topic: http

Firefox 49 implemented a new extended attribute of the Cache-Control response header - immutable, it has not been standardized yet, see this post for the details.

So here is the conflict: should fetch(aURLWithImmutableCache, {cache: "no-cache"}) send a conditional request first or use the cache directly without sending any request? Currently Firefox's behavior is the latter.

Dominant language
HTML
Stars
2.3k
Forks
403
Avg merge
21h 16m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from whatwg/fetch

All issues in whatwg/fetch

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.