Hiya @nocodebenny and thanks for the polite and thoughtful question! Hope your holidays have been swell too - and, I hope that the swelling doesn’t go down for some time yet 
Dad jokes aside, you most likely wouldn’t want to reverse proxy in an edge function. You can absolutely make outgoing network connections and the time awaiting response generally isn’t included in this limit, but the 50ms max CPU runtime relies on you doing whatever else you’ll do, very quickly, and if your remote service (us, webflow, something else) returns data somewhat slowly…I think we could run out of that 50ms processing data bit by bit before the transmission is completed. So I would suggest redirecting or modifying HTML in an edge function, and doing potentially-long-running network operations in a lambda or using our redirects.
I wonder if you could share your existing config in more detail so we could understand what is failing with it? I’m hoping for something like this:
- I host xyz.com on Netlify
- I host subdomain.xyz.com on webflow
- visit uses browser to go to subdomain.xyz.com on webflow
- I want webflow to instead place the visitor, with URL updated in browser, at .xyz Domain Names | Join Generation XYZ
- which is served by the netlify site, and as you can see, there is a file at /subdomain on the xyz.com site, so I don’t understand the redirect loop
We don’t know anything about how webflow works and won’t be able to become experts, but including your actual netlify sites, and hostnames, so we can see your configuration here, and in DNS, will make our analysis much more directly helpful, and waste less of our time guessing at a theoretical setup, if you wanted to give us a real holiday present as we try to help you troubleshoot 