azure-front-door

问题 Azure Front Door doesn't forward the Authorization header bearer token to the endpoint. All other headers are passed along fine except this one. Standard headers (such as Accept) are passed through, made-up headers (such as 'OtherHeader') are passed through as well, while key-based security headers (such as 'Ocp-Apim-Subscription-Key') are also passed through fine. The routing rules are set to perform a 302 (Found) Redirect as we're performing IP filtering at the endpoint and this type of

问题 I have multiple sites hosted on the same machine in Azure on different ports: foobar.com:8000 foobar.com:8001 foobar.com:8002 etc I would like to address these by subdomain using a reverse proxy; aaaa.mysite.com ----> foobar.com:8000 bbbb.mysite.com ----> foobar.com:8001 cccc.mysite.com ----> foobar.com:8002 Is it possible to do this in Application Gateway? It only seems to cater for different paths (not subdomains) and doesn't allow ports to be specified for backends. Is there another Azure

来源： https://stackoverflow.com/questions/62461510/how-to-configure-web-apps-such-that-they-cannot-be-accessed-directly

问题 I'm wondering if anyone else has had this issue with Azure Front Door and the Azure Web Application Firewall and has a solution. The WAF is blocking simple GET requests to our ASP.NET web application. The rule that is being triggered is DefaultRuleSet-1.0-SQLI-942440 SQL Comment Sequence Detected . The only place that I can find an sql comment sequence is in the .AspNet.ApplicationCookie as per this truncated example: RZI5CL3Uk8cJjmX3B8S-q0ou--OO--bctU5sx8FhazvyvfAH7wH . If I remove the 2

问题 I have three backend pools, 1 is an API and 2 are Web Apps. I've set up routing in Azure Front Door to route to the correct areas, but how do I modify the web apps to use the Front Door URL for all of the links without having to hardcode them all manually? For example, if the Front Door URL is frontdoor.azurefd.net but Web App 1 is published to webapp1.azurewebsites.net how can I set the root url of webapp1 such that all of the Razor Areas actually link to frontdoor.azurefd.net/webapp1? 回答1:

问题 Domain in Azure Front Door: www.foobar.com Azure Web Apps: foobar-web foobar-api I would like to be able to have www.foobar.com pull up the web app foobar-web and utilize /api in the url to access the web app foobar-api . www.foobar.com -> foobar-web www.foobar.com/api -> foobar-api I have a backend pool setup for each and route rules setup. Each time I try navigating to www.foobar.com/api the url in the browser changes to foobar-api.azurewebsites.net/api , but if I navigate to www.foobar.com

问题 I've been working with an Azure support engineer to try and figure this out, and he has not been able to determine the issue, so I'm hoping someone here has run into this scenario: We have set up our first Azure Front Door - the configuration at this stage is very simple - the backend pool consists of just one of our web apps (an Azure App Service), and one route which just forwards all requests from the front door URL to the web app URL. The issue: every request we send provides a 403

问题 I got AFD with 1 FE web app on it. I want to add another web application that hold maintenance/sorry page. All URLs from FE need to be cached, sorry page image must not be cached. I tried to add my sorry page web app to same backend pool with low priority and weight. When i turn off FE, it redirect to sorry page web app, but it caches content. And as i understood, i cannot use another backend pool (to disable caching ), cause 2 pools cannot be connected to same AFD FE endpoint. Any thoughts

问题 I got AFD with 1 FE web app on it. I want to add another web application that hold maintenance/sorry page. All URLs from FE need to be cached, sorry page image must not be cached. I tried to add my sorry page web app to same backend pool with low priority and weight. When i turn off FE, it redirect to sorry page web app, but it caches content. And as i understood, i cannot use another backend pool (to disable caching ), cause 2 pools cannot be connected to same AFD FE endpoint. Any thoughts

问题 I want to to be able to serve a SPA using just the Azure Front Door / and not Azure CDN. Looks like the Front Door provides the caching that the CDN would provide and I can add multiple regional storage accounts to it, making it global at scale. The problem is, I can't match the path to index.html files. Found this feedback and it looks like this can be solved using the URL rewrite and redirect but couldn't figure out how. I have /test/ and /test to match with the route below, so it should be