The Python flask application https://gitlab.wikimedia.org/toolforge-repos/ifttt behaves differently when deployed as the "ifttt" tool vs any other toolname. Specifically the /ifttt/v1/... routes in the application return an unexpected 404 response when deployed as https://ifttt.toolforge.org/ifttt/v1/.... Changing the called URL to https://ifttt.toolforge.org//ifttt/v1/... (double solidus to start the path) produces the expected responses from the application.
When the tool name is anything other than "ifttt", for example "ifttt-bd808" or "ifttt-dev", the URLs work as expected. It took me a couple of days to convince myself that this is a bug outside of the code and configuration I have been working on for T294448: <Break-Fix> IFTTT integration: fix or sunset?.
I think this behavior is related to the --mount "/$TOOL=$HOME/www/python/src/app.py" cli arguments added to the uwsgi command that is executed inside of the kubernetes container. The documentation is a bit confusing, but I think this line was needed prior to T234617: Toolforge. introduce new domain toolforge.org and is now unnecessary. The fact that things work as generally expected when the $TOOL is not the same as the first path component of the route may be related to https://github.com/unbit/uwsgi/issues/1935