Redirect http to https clarification

[jeroenwo]

At bullet 10 (creating the redirect http to https rule), can there be some clarification on the following points:

• Why is 302 used? I would expect it to be permanent (it isn't like we want to revert to http again in the future, and less traffic/redirects from FrontDoor is desirable).
• Why is 302 chosen (allows changing POST to GET) over 307/308, where changing POST to GET is not allowed?

---

Document Details

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

• ID: 908053a8-ebc0-35ec-87ad-24e59f587eb9
• Version Independent ID: c8b90a6a-c37f-68eb-1e1d-54322eae9324
• Content: Create a Front Door with HTTP to HTTPS redirection using the Azure portal
• Content Source: articles/frontdoor/front-door-how-to-redirect-https.md
• Service: frontdoor
• GitHub Login: @sharad4u
• Microsoft Alias: sharadag

[KrishnaG-MSFT]

@jeroenwo Thanks for your comment. We will review and get back to you shortly with an update.

[SubhashVasarapu-MSFT]

@jeroenwo , We have assigned this issue to the content author for insights.

[duongau]

reassign: jessie-jyy

[Harikrishnan-M-B]

The redirect type can be set to 301/302/307/308 per customer needs. 301 is the recommended status code for HTTP to HTTPS redirection. See URL redirect

The instructions in Create a Front Door with HTTP to HTTPS redirection is recommending 302 which is inconsistent with the first link. We will fix this. Thanks for pointing this out @jeroenwo

[duongau]

The article has been updated and should reflect later today. Will archiving this issue for now. Please feel free to contact us if you have any questions. #please-close