Menu
In MVC we can decorate action methods with different filters like
[HttpPost] [Authorize] public ActionResult mymethod(){} HttpPost derives from MethodSelectorAttribute (probably indirectly) and the Authorize attribute inherits from ActionFilterAttribute.
My question is: in which order are they executed in the MVC request pipeline? I tried to go search in MVC source code but failed to find the relevant code bits.
616
in the request life cycle, after the URL Routing module has selected the route and controller have been initialized, the first thing that kicks off in the Action method execution is Authentication Filter.
Filters execute in this order: Authorization filters. Action filters. Response/Result filters.
Filters run in the following order: Authorization filters. Action filters. Response filters.
Exception Filters − Exception filters are the last type of filter to run. You can use an exception filter to handle errors raised by either your controller actions or controller action results.
Filters run in the following order:
For example, authorization filters run first and exception filters run last. Within each filter type, the Order value specifies the run order. Within each filter type and order, the Scope enumeration value specifies the order for filters. This enumeration defines the following filter scope values (in the order in which they run):
Extracted from MSDN
70
To save you some time, this is how you set the order:
[MyCustomContextFilter(Order=1)] The index is 0 based, so you can do 0, 1, 2, etc...
It should be noted that just because a filter is on the base class doesn't tell MVC to apply it first :(.
40
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
