Override Exception Filters executed last instead of first about autofac.webapi HOT 3 OPEN

Interesting. Sounds like something to address if it's inconsistent with the action filter ordering.

I will say it's odd that you're registering overrides before registering the things to override. Registration order has always been important in DI. If you register them in the order of "not overrides" and then "overrides" what happens?

And, just to verify, if you do this same thing with action filters it provides the expected order?

from autofac.webapi.

The order does not appear to change what happens for the exception filters or action filters

from autofac.webapi.

Huh. Well, I guess that's something to fix. Might not be too hard if you want to throw a PR at us.

from autofac.webapi.