Add support for redirects on 410 responses#155
Conversation
|
@jevgenijsp @kaspars-ozols @marisks |
7c225f8 to
64ce4c1
Compare
|
@ErvinsA I've made adjustments to this PR in regards to your feedback. |
|
Pipeline was broken due to .net 6 no longer being supported. I updated the csproj files to use .net 8 instead |
|
@ErvinsA Looks like the "build" works after updating to .net 8 but there seems to be a issue with SonarCube |
|
I think this is good to go to release! |
|
@ErvinsA Looks like there is still a issue in the pipeline related to SonarQube, |
|
There is problems with SonarQube and pullrequests so that can be ignored. |
|
@ErvinsA Great! |

In Optimizely, expired pages respond with a 410 http response which is ignored by the NotFound Handler.
This PR adds a option to enable the redirect manager to work on 410 responses.