Closed timgaunt closed 8 years ago
Very similar to conflict of the response filters. It is also possible, that the filters specified in wrong order.
Give me an example of FilterConfig.cs
file and the problematic MVC action.
Sure, although it's working on other pages on the site (same code base -and has worked on this page before...!?!)
GlobalFilters.Filters.Add(new MinifyHtmlAttribute());
GlobalFilters.Filters.Add(new MinifyXmlAttribute());
GlobalFilters.Filters.Add(new CompressContentAttribute());
Try the following:
GlobalFilters.Filters.Add(new CompressContentAttribute());
GlobalFilters.Filters.Add(new MinifyHtmlAttribute());
GlobalFilters.Filters.Add(new MinifyXmlAttribute());
Done and no luck, I've even removed any other filters that were around in the project without any benefit.
I've found the issue (and this is an interesting one).
In short, we'd renamed an action that was being referenced on the page, when I disabled the filter completely I get the error "A public action method 'ActionName' was not found on controller 'xxx.www.Controllers.SomeController'." which when resolved makes the system "just work".
Could it be that it's trying to minify responses with response codes != 200?
Could it be that it's trying to minify responses with response codes != 200?
In this case, is performed compression only. Will fix in next release.
In WebMarkupMin 2.0.0 RC 3 fixed this error.
i use GlobalFilters.Filters.Add(new CompressContentAttribute()); GlobalFilters.Filters.Add(new MinifyHtmlAttribute()); GlobalFilters.Filters.Add(new MinifyXmlAttribute()); now i want exclude one action from it please guide me
Hello, Mahmoud!
Read the “ASP.NET Extensions > Managers and options” subsection and “ASP.NET 4.X Extensions” section of documentation.
Running WebMarkupMin.AspNet4.Mvc v2.0.0-rc1 on Umbraco Cms 6.2.5 (https://www.nuget.org/packages/UmbracoCms/6.2.5) with MinifyHtmlAttribute/MinifyXmlAttribute/CompressContentAttribute enabled we're getting "Filtering is not allowed" on one or two actions.
What's interesting is the module appears to be working generally throughout the site, it's even been working on this action before a recent build (that included no related changes).
Full stack trace is below:
Server Error in '/' Application.