Azure Front Door
An Azure service that provides a cloud content delivery network with threat protection.
712 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 59%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECM%3C/text%3E%3C/svg%3E)
@Martin Hinshelwood nkdAgility.com
Thank you for reaching out. I think the issue might be due to host name preservation as described in the article here
https://zcusa.951200.xyz/en-us/azure/architecture/best-practices/host-name-preservation
We recommend that you preserve the original HTTP host name when you use a reverse proxy in front of a web application. Having a different host name at the reverse proxy than the one that's provided to the back-end application server can lead to cookies or redirect URLs that don't work properly.
A common and more specific case of the previous scenario occurs when absolute redirect URLs are generated as described here.
The documentation does not specifically talk about static web apps as backend but The recommendation to preserve the host name typically still applies for any components in your application that depend on it, unless you specifically make your application aware of reverse proxies and respect the forwarded or X-Forwarded-Host headers, for example.
Update 12/12:
Thank you for your patience here, I just heard back from the team and the approach above for host name preservation is recommended by them in this scenario.
Hope this helps! Please let me know if you have any additional questions. Thanks