Azure-docs: Does Front Door supported HTTP to HTTPS redirection?

[nnasaki]

I wanna elect to redirect HTTP traffic to HTTPS as-is Using the Azure CDN to access blobs with custom domains over HTTPS | Microsoft Docs. Does Front Door supported ?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 6b393c2f-c603-6287-743f-9c169673ce41
• Version Independent ID: 475325a1-e953-2723-b626-80ea86a4d347
• Content: Azure Front Door Service - URL Rewrite
• Content Source: articles/frontdoor/front-door-url-rewrite.md
• Service: frontdoor
• GitHub Login: @sharad4u
• Microsoft Alias: sharadag

[MarileeTurscak-MSFT]

@nnasaki
Thanks for your feedback! We will investigate and update as appropriate.

[nnasaki]

@MarileeTurscak-MSFT Thank you! I'm looking forward to!

[TravisCragg-MSFT]

@nnasaki I have reached out to get more information, and will update you as soon as I am able.

[TravisCragg-MSFT]

@nnasaki it is not supported at this time. You can leave your feedback Here if you would like this feature to be enabled in the future.

[TravisCragg-MSFT]

@nnasaki We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

[nnasaki]

@TravisCragg-MSFT I would like to easily redirect from HTTP to HTTPS. For example, in the AWS Cloud Front, you can do it by simply turning on the check box.

I do not want to implement such a basic function in the application. At the very least I will choose to use the AWS Cloud Front.

[thiezn]

+1 for http redirection! Love the simplicity of configuring the front door service, especially compared to Azure application gateway. Enabling HTTP to HTTPS redirection will allow us to not have to deal with that on the backend.

[daveaglick]

Another +1 for http -> https and leaving other components of the URI intact (to be processed in the subsequent request by any URL rewriting, etc.)

[SergeBerwert]

I would love to have that too!

[TravisCragg-MSFT]

@nnasaki @thiezn @daveaglick @SergeBerwert This feature is currently being worked on, and you can Upvote the Feature Request Here! You can also make additional suggestions or provide additional as well.

[katafractari]

A tip from Nathan J. Robinson's comment on the feature upvote page worked for me:

This is now supported, although not yet documented. You can add a new routing rule and set the "Accepted Protocol" to "HTTP Only", "Route Type" to "Redirect", "Redirect Protocol" to "HTTPS Only", and "Destination Host" to your Front Door host name. Set the "Accepted Protocol" on all your other routing rules to "HTTPS Only". This works to redirect HTTP to HTTPS.

[Philo]

A tip from Nathan J. Robinson's comment on the feature upvote page worked for me:

This is now supported, although not yet documented. You can add a new routing rule and set the "Accepted Protocol" to "HTTP Only", "Route Type" to "Redirect", "Redirect Protocol" to "HTTPS Only", and "Destination Host" to your Front Door host name. Set the "Accepted Protocol" on all your other routing rules to "HTTPS Only". This works to redirect HTTP to HTTPS.

While this does work, it requires a second routing rule, with a service charging model based on number of routing rules I feel there should be something more intrinsic to the service to support this.

[Zenuka]

The documentation has been updated with this workaround: https://docs.microsoft.com/en-us/azure/frontdoor/front-door-how-to-redirect-https

[rooque]

A tip from Nathan J. Robinson's comment on the feature upvote page worked for me:

This is now supported, although not yet documented. You can add a new routing rule and set the "Accepted Protocol" to "HTTP Only", "Route Type" to "Redirect", "Redirect Protocol" to "HTTPS Only", and "Destination Host" to your Front Door host name. Set the "Accepted Protocol" on all your other routing rules to "HTTPS Only". This works to redirect HTTP to HTTPS.

While this does work, it requires a second routing rule, with a service charging model based on number of routing rules I feel there should be something more intrinsic to the service to support this.

I agree. It doesn't make sense to pay a routing rule just to redirect http to https.