Azure Front-door TCP_MISS even with Cache-Control: public
The Azure Front-door honours the cache headers from origin, so I can see the
Azure Front Door URL rewrite to lowercase and segment url_path
We have a website https://www.example.com/detail/nameXXX/abcDEF, and we want to redirect to https://www.example.com/detail/abcdef. The rules are blow:
How to setup backend frontdoor redirect to destination link has special characters
I have a request config redirect link on frontdoor, but the destination link has special characters, so I have to encode path of URL to setup Destination path, but it could not resolve link encode when redirected to the destination URL. Does anyone have any experience with this
Request was routed from a verified domain which is not CustomUrlDomain
I have a front door setup that has been working for many months. Now all of a sudden I am getting:”AADSTS399280: Request was routed from a verified domain which is not CustomUrlDomain.”
URL redirect in azure front door with query string
can we do the following URL Rewrite using azure front door? the requirement is to modify the last path /customer1 to a query string for the backend origin.