Caching / re-load from database

[nma76]

Hi,
I just noticed that when using Redirection Manager with database replication, the server using the replicated database doesn't pick up the new rules added. I can see that the rule is replicated and do exist in the database, but the server do not redirect the new url. Restarting the app-pool ofc picks up the new rules.

Is there any configuration i can do to make the replicated server aware that new rules has been added? Or can i force it to reload from database in any way?

[evest]

This was added in the .NET Core repo, it should be possible to back-port here: https://github.com/Geta/geta-notfoundhandler/blob/master/src/Geta.NotFoundHandler.Optimizely/Core/Events/OptimizelySyncEvents.cs

An "outside" workaround would be to add an API or controller on your site, that uses the Episerver event system to post a similar message to clear the 404 cache. Episerver will distribute the event to all servers, and you write the code that clears the cache. Next request would build the cache again.