OutputCache seems to be ignoring the Location option in ChildAction within.
If you specify, such as OutputCacheLocation.None, the option not to cache on the server side, the server tries to cache the case of ChildAction. This can be affected when you specify OutputCacheLocation.None in GlobalFilter.
```
public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{
filters.Add(new OutputCacheAttribute { Location = OutputCacheLocation.None });
}
```
InvalidOperationException will be thrown if you call the ChildAction in this setting. OutputCache has been specified at the time of None, it should not enable cache.
I have sent a pull request. We would appreciate if you could confirm.
https://aspnetwebstack.codeplex.com/SourceControl/network/forks/shibayan/aspnetwebstack/contribution/4323
If you specify, such as OutputCacheLocation.None, the option not to cache on the server side, the server tries to cache the case of ChildAction. This can be affected when you specify OutputCacheLocation.None in GlobalFilter.
```
public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{
filters.Add(new OutputCacheAttribute { Location = OutputCacheLocation.None });
}
```
InvalidOperationException will be thrown if you call the ChildAction in this setting. OutputCache has been specified at the time of None, it should not enable cache.
I have sent a pull request. We would appreciate if you could confirm.
https://aspnetwebstack.codeplex.com/SourceControl/network/forks/shibayan/aspnetwebstack/contribution/4323