You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to be able to redirect www. => naked domain. Options:
Without writing any code, we already have a redirect backend, but our design assumes one backend per app, so we'd have to write separate app for the redirect. => not good
Support multiple backends per app (override with redirect backend on www. hostname). This is the only use case that requires it => not good
Just have a flag on the frontend that it should redirect to naked domain, and have Edgerouter handle that internally somehow. That feels a bit dirty though, too.
Currently we're using Cloudflare page rules for this, but I don't like it because I like the idea of turning Cloudflare off and not having behavioural changes
The text was updated successfully, but these errors were encountered:
Now we have:
We want to be able to redirect www. => naked domain. Options:
The last idea looks something like:
Currently we're using Cloudflare page rules for this, but I don't like it because I like the idea of turning Cloudflare off and not having behavioural changes
The text was updated successfully, but these errors were encountered: