title: Why is order int.MaxValue - 10 used for IOrderedFilter and which order to use for additional filters?
body: <p>I am trying to implement an additional filter into an ASP.NET Core 6 based web application. Right now, there is already a filter implemented which handles certain http exceptions in <code>OnActionExecuted</code>. This filter implements the <code>IOrderedFilter</code> interface and has its <code>Order</code> defined like this:</p>
  <pre><code>public int Order =&gt; int.MaxValue - 10;
  </code></pre>
  <p>The new filter which I want to implement should run right before the code inside the controller actions is executed. Now I have two questions about this:</p>
  <ol>
  <li>Why is <code>int.MaxValue - 10</code> used for the first filter? I've also seen this same way of specifying the order in a few examples on various sites but I do not understand why exactly anyone would use this exact number. Is there any reason for this?</li>
  <li>Which order should I use for my new filter? Or does that not matter because, unlike the other filter, it should execute before the controller actions?</li>
  </ol>