feat(backwards compatible): support for onredirect middleware #3858
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #3857
Example:
Calling this server at
GET /foo/
responds with a 307 Response with Location:/foo
and Response Header asX-Foo: Bar;
Just like this, even CORS-mitigation headers can be applied as well
A note on backwards compartibility
This PR complies with backwards compatibility by ensuring that the behaviour of a Gin with no explicitly attached
redirectMethod
-HandlerChain to the engine identically works like it worked in the past.Only when a developer explicitly uses the
.OnRedirect
method on their GIn engine makes them leverage the functionalities offered by this PR