The popular NotFound handler for ASP.NET Core and Optimizely, enabling better control over your 404 page in addition to allowing redirects for old URLs that no longer works.
Is their a reason for not allowing regex redirects to have the option between permeant or temporary similar to how normal redirects work? I know that Regex redirects are in beta but from the code the change should be similar to normal redirects so I can take a look at it if there isn't a reason behind forcing them to temporary.
Previously during the development of Regex Redirects the default redirect type was set to permeant. This was changed with this https://github.com/Geta/geta-notfoundhandler/pull/49/commits/95459dc4aa044469fca2c353f048f6312343200e PR which was apart of the regex redirect branch.
Is their a reason for not allowing regex redirects to have the option between permeant or temporary similar to how normal redirects work? I know that Regex redirects are in beta but from the code the change should be similar to normal redirects so I can take a look at it if there isn't a reason behind forcing them to temporary.