Skip to content

refactor: Move ETag to its own plugin #54

Description

@ardalanamini

The ETag header and freshness calculation related to the header in response can be moved to their own plugin as it's not always needed in all APIs (e.g. micro-services that have their own caching layer and don't depend on HTTP caching headers)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestperformanceIssues or pull requests related to performancetriagePull requests & Issues in need of review for relevancy/actionability & readiness

    Type

    No type

    Projects

    • Status
      Triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions