Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

configurable authorization header checking in ResponseCachingPolicyProvider #15359

Closed
namnik opened this issue Oct 24, 2019 · 1 comment
Closed
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares
Milestone

Comments

@namnik
Copy link

namnik commented Oct 24, 2019

I need to use response caching despite exist authorization key in request header!
I know security issues about authorization header when using response caching.
but can configurable and optional to use this validation in the response caching Middleware?

I notice that both class and interface for this validation: ResponseCachingPolicyProvider and IResponseCachingPolicyProvider is Internal.

        if (!StringValues.IsNullOrEmpty(request.Headers[HeaderNames.Authorization]))
        {
            context.Logger.RequestWithAuthorizationNotCacheable();
            return false;
        }
@jkotalik jkotalik added this to the Backlog milestone Oct 31, 2019
@jkotalik
Copy link
Contributor

Dup of #14569

@ghost ghost locked as resolved and limited conversation to collaborators Dec 2, 2019
@amcasey amcasey added area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares and removed area-runtime labels Jun 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares
Projects
None yet
Development

No branches or pull requests

5 participants