Hey Chris, I haven’t worked with cloudfront or these specific reverse proxy configs, but try this-
Pick any page on your first website, e.g. your
/about page, and try to access it as;
( with the trailing slash )
Does it redirect you to
www.domain.com/about or does it redirect you to
If you get the first one ( the desired behavior ) than your configuration for your 1st site is handling redirects ok, and your 2nd site is missing a piece of the config that your 1st site has.
Most webserver redirect request paths with a trailing
/ ( except the root path ) when they cannot find a matching directory or default file in that directory. Webflow doesn’t have a concept of default files, so all
/path/ requests get redirected to
/path. That’s standard practice in this situation.
However from your description, site 2 is identifying itself as
my2ndsite.domain.com, and the redirects it’s doing include that.
Here’s an example redirect on one of my sites, you can see that the response includes the absolute URL to redirect to.
If the test I presented is working, than the proxy config of your first site resolves that.
Without digging through those config docs, my off-the-top-guess would be that the problem is your second site’s Webflow settings under Custom Code / Advanced. I would guess that they should be something like;
Hope that points you in the right direction.
If you need more, share your actual URLs, so I can have a look at what Webflow is responding with. That will offer more clues.