-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Localization & Output Caching #2652
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
Comments
From @Eilon on Thursday, September 17, 2015 4:32:11 PM There are no features currently planned for directly solving this. The correct approach at this time is to set the appropriate VaryBy headers on the response. |
From @Eilon on Thursday, September 17, 2015 8:29:49 PM It needs to be done by the user manually. |
Thanks for contacting us. We're closing this issue as there was no community involvement here for quite a while now. |
This issue from the first days of DNX :) no problem if it's closed, while there's a caching mechanism built in the localization APIs |
From @hishamco on Wednesday, June 24, 2015 11:31:06 AM
I'm wondering if the Output Caching will block the localization APIs from retrieving the right values for the current culture, or shall we need sort of
VaryByCustom
to update the correct values based on the current culture/cc @DamianEdwards
Copied from original issue: aspnet/Localization#40
The text was updated successfully, but these errors were encountered: