Thnxx @julian ! and congrats to all the team for all this awesome work on nodebb !!
I'm a little bit puzzled by your answer, and maybe i'm not getting it right.
So, indulge me with a more thorough explanation of my use case :
I've allready have put nginx in front of nodebb with this classic configuration :
It handles all the static assets and then call nodebb for the dynamics parts.
So, now, i just have to deal with something like 100-500 old topics (that have been correctly rewritten to our new nodebb urls with a different set of nginx redirect rules) but they are not here anymore, and i want to find redirections to new topics for the part of them that are the most requested..
It's really an SEO thing : we don't want to loose the good rankings the old forum had.
These old topics are have been indexed by google or some old facebook post and they are really frequently requested ...
But i don't see the interest to put these (hundreds?) of special redirections rules inside nginx that handles allready every single request to nodebb ?? That would put a serious (indue) work on him on every request ?
I really dream of a core nodebb plugin that could handle all these 404 inside nodebb when everything else have been tried (so that it would be a very scarce event).
Like i've said before : it's really a use-case of dealing with a post-migration trauma because these 404 will for sure disappear with time and the new google indexations.. but we want to address them now so that we dont loose ranks...
My boss is really watching the 404 pages as they happen, and he could deal with them in the back-office, but for sure he doesn't want to edit the nginx configuration files and me neither when a new 404 is detected...