A “proxy” is typically configured on the client side, for the person browsing. Whereas a “reverse proxy” sits in front of a website on the receiving end. A reverse proxy serves a different function:
You might use it for intelligent routing as the @Emmanuel_Evarist is doing, sending some URLs to backend server A, while other URLs go to backend server B. Or you might be needing some additional security like bot and spam protection. Cloudflare for instance offers proxy servers that do this (but be careful, you will run into certificate renewal problems if you use this with Webflow).
@Emmanuel_Evarist I would probably solve that by putting the toml file at a different subdomain so I wouldn’t have to go through the hassle of setting up a reverse proxy. Then you could either link to the file or put it in an iframe.