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

Issue with external outputcache #113

Open
ZNS opened this issue Feb 15, 2017 · 2 comments
Open

Issue with external outputcache #113

ZNS opened this issue Feb 15, 2017 · 2 comments

Comments

@ZNS
Copy link

ZNS commented Feb 15, 2017

Hi,

I've implemented outputcaching using redis for umbraco, by writing my own OutputCacheProvider. However I get an exception with client dependency when running multiple sites that share the same redis store. One site tries to access the other sites app_data\clientdependency folder.

@ZNS
Copy link
Author

ZNS commented Feb 15, 2017

It seems a workaround for this is to override the getoutputcacheprovidername method.

public override string GetOutputCacheProviderName(HttpContext context)
{
    if (context.Request.Url.AbsolutePath.Equals("/umbraco/dependencyhandler.axd", StringComparison.InvariantCultureIgnoreCase))
    {
        return "AspNetInternalProvider";
    }
    return base.GetOutputCacheProviderName(context);
}

It would be nice if this could be solved within the library itself though.

@samgooch
Copy link

Hi @ZNS - I'm too facing this issue now with Umbraco 8.10.1 and using Azure Redis Cache. The above doesn't seem to work for me. I'm seeing Object Reference errors around the provider (is my guess). Have you had to do anything for newer versions of Umbraco?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants