As discussed in the team meeting this task will be restricted to providing a solution for the revertrisk-language-agnostic that currently handles these redirects by rewriting the hosts from the values available in a configuration file. We want to remove this "hack".
Also, a potential idea would be to allow only a specific number of redirects (e.g. up to 3).

Once we figure out a nice way to deal with redirects we will implement and roll them out in all the other model servers in another task(s).

Updates:

I worked on this a while ago and created a patch for mwapi's async_session.py, but it didn't function as expected when I tested it today. The idea was to update the api_url of the mwapi.AsyncSession with the new url returned in the Location header. However, for some reason it didn't redirect to the new url in subsequent requests, ended up running into the too many redirects error.

Behind mwapi, we use aiohttp.ClientSession to call MW API. P67828 is an example that only uses aiohttp which demonstrates the idea in the patch, and it works as expected. That said, mwapi adds additional complexity to this task. We need to figure out why it's not working within mwapi.

Alternatively, we could handle redirects in the code that calls mwapi, rather than within mwapi itself. This could be done in the model server's code or knowledge integrity, though it might not simplify the solution. P67830 shows an example where redirects are managed in the function calling the request, not within the request itself.