Add more functions to HttpCachePolicy

[TaoziZ03]

Summary

Can I add more functions to HttpCachePolicy?

1. SetNoStore(): add no-store header
2. SetETag(string etag): add etag header
3. UpdateHeaders(): better support no cache scenario, set expires = -1, pragma = no-cache and omit vary.

Motivation and goals

Our legacy code has a custom wrapper of HttCachePolicy and was modfied throughout whole request lifetime. None of attribute and middleware fit in existing design. To skip the design change and migrate to .net core first, I hope to add these functions.

In scope

A list of major scenarios, perhaps in priority order.

Out of scope

Scenarios you explicitly want to exclude.

Risks / unknowns

Please kindly point out other files I should modify.

Examples

Give brief examples of possible developer experiences (e.g., code they would write).

Don't be deeply concerned with how it would be implemented yet. Your examples could even be from other technology stacks.

[twsouthwick]

We'll take an implementation of this if you'd like to provide that

[TaoziZ03]

I hope HttpCachePolicy could have the same behavior as Framework version.

systemweb-adapters/src/Microsoft.AspNetCore.SystemWebAdapters/HttpCachePolicy.cs

Line 11 in 649e737

public class HttpCachePolicy

Framework reference:
Get/SetNoStore()
Get/SetETag()
UpdateCachedHeaders()

Repro:

// Here set `vary` and `Expires`
httpContext.Reponse.SetVaryByCustom("accept-encoding");
httpContext.Reponse.SetExpires(2d);
httpContext.Response.Cache.SetETag("ETag1");
....
httpContext.Response..Cacheability = HttpCacheability.NoCache;
httpContext.Response.Cache.SetNoStore();

Expected headers

Cache-Control: no-store, no-cache
Pragma: no-cache

ETag, Expires and Vary will ignored because later set cachebility to NoCache.