Skip to content

Cache related warning headers #2619

Closed
Closed
@aspnet-hello

Description

@aspnet-hello

From @JunTaoLuo on Thursday, September 15, 2016 2:50:04 PM

Need to revisit this to see what warnings we may want to send along with cached responses. For example, if no original expiry information is explicitly stated, we currently use a default expiration of 10s. In this case, we should send the warning 113 - "Heuristic expiration"

Copied from original issue: aspnet/ResponseCaching#41

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

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions