Open Bug 2038013 Opened 1 month ago Updated 2 hours ago

[no-vary-search] Enable no-vary-search http caching extension for release users

Categories

(Core :: Networking: Cache, enhancement, P2)

enhancement

Tracking

()

ASSIGNED
Tracking Status
relnote-firefox --- ?
firefox153 ? affected

People

(Reporter: smayya, Assigned: smayya, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 file)

No description provided.
Severity: -- → N/A
Priority: -- → P2
Whiteboard: [necko-triaged]

Release Note Request (optional, but appreciated)

[Why is this notable]: This is a new web platform feature and developers would be interested in the support of this feature.

[Suggested wording]:
Added support for the No-Vary-Search HTTP response header for the HTTP disk cache. Servers can now declare which URL query parameters are irrelevant to the response, allowing Firefox to reuse cached resources across parameter variations and improving cache hit rates.

[Links (documentation, blog post, etc)]:

https://httpwg.org/http-extensions/draft-ietf-httpbis-no-vary-search.html

[Tracking Requested - why for this release]: enable no-vary-search for release users.

We need to flip the pref.

Does it have a webcompat impact? It was recently activated in nightly and it doesn't seem that there are metrics set up to study the use of this header as Bug 2038028 is not fixed.

Flags: needinfo?(smayya)
Assignee: nobody → smayya
Status: NEW → ASSIGNED

I would say the webcompat risk is minimal here as failure to support or improper handling this will only lead to more network requests.
I also have a patch for Bug 2038028 (which can easily uplift).
However, I am okay in differing this to 154 if you insist as we don't have a hard target for 153.

Flags: needinfo?(smayya) → needinfo?(github.lld)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: