Skip to content

No-cache fields #2620

New issue
New issue
Closed
Closed
No-cache fields#2620
Labels
affected-very-fewThis issue impacts very few customersarea-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-response-cachingseverity-nice-to-haveThis label is used by an internal tool
Milestone
 
Backlog
@aspnet-hello

Description

@aspnet-hello
aspnet-hello
opened on Jan 2, 2018

From @JunTaoLuo on Thursday, September 15, 2016 2:45:33 PM

Some directive such as no-cache may contain fields which can be stripped from the response after which the response can be deemed cacheable.

Copied from original issue: aspnet/ResponseCaching#40

Metadata

Metadata

Assignees

No one assigned

    Labels

    affected-very-fewThis issue impacts very few customersarea-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresenhancementThis issue represents an ask for new feature or an enhancement to an existing onefeature-response-cachingseverity-nice-to-haveThis label is used by an internal tool

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions