Skip to content
This repository has been archived by the owner. It is now read-only.

Cache-Control Immutable HTTP Header #763

Eilon opened this issue Jan 30, 2017 · 3 comments


None yet
4 participants
Copy link

commented Jan 30, 2017

From @RehanSaeed on January 27, 2017 9:3

There is a new immutable extension to the Cache-Control HTTP header which has been adopted into the IETF on the Standards Track. It's currently implemented in Firefox 49. The documentation states:

Indicates that the response body will not change over time. The resource, if unexpired, is unchanged on the server and therefore the client should not send a conditional revalidation for it (e.g. If-None-Match or If-Modified-Since) to check for updates. Clients that aren't aware of this extension must ignore them as per the HTTP specification. In Firefox, immutable is only honored on https:// transactions.

Read More here:

Facebook and the BBC have implemented this extension with significant performance wins. Since this is a draft spec, ASP.NET Core should probably not implement it just yet but raising this issue to put it on the radar. If another browser should implement this feature, perhaps it should be considered even as a draft.

Copied from original issue: aspnet/Mvc#5723


This comment has been minimized.

Copy link

commented Jan 30, 2017

@muratg muratg added this to the Backlog milestone Feb 3, 2017


This comment has been minimized.

Copy link

commented Feb 3, 2017

Since the extension to the HTTP header is currently a draft, putting this in backlog.


This comment has been minimized.

Copy link

commented Jan 2, 2018

This issue was moved to aspnet/AspNetCore#2712

@aspnet aspnet locked and limited conversation to collaborators Jan 2, 2018

@aspnet-hello aspnet-hello removed this from the Backlog milestone Jan 2, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.