-
Notifications
You must be signed in to change notification settings - Fork 20
Add support for redirects on 410 responses #155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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.