[ ] š Documentation (updates to the documentation or readme)
[x] š Bug fix (a non-breaking change that fixes an issue)
[ ] š Enhancement (improving an existing functionality like performance)
[ ] āØ New feature (a non-breaking change that adds functionality)
[ ] ā ļø Breaking change (fix or feature that would cause existing functionality to change)
š Description
Resolves #2758
I think the rootRedirect.statusCode was ignored because the request was redirected twice, once from / to the configured rootRedirect.path (e.g. about) with the statusCode, then again because /about doesn't exist for strategy prefix so it will be redirected to /en/about while ignoring rootRedirect configuration, as it's no longer redirecting on root.
This PR changes rootRedirect to try and translate the redirect path, so that a single redirection happens with the configured status code.
š Linked issue
2758
ā Type of change
š Description
Resolves #2758
I think the
rootRedirect.statusCodewas ignored because the request was redirected twice, once from/to the configuredrootRedirect.path(e.g.about) with the statusCode, then again because/aboutdoesn't exist for strategyprefixso it will be redirected to/en/aboutwhile ignoringrootRedirectconfiguration, as it's no longer redirecting on root.This PR changes
rootRedirectto try and translate the redirect path, so that a single redirection happens with the configured status code.š Checklist