Aspnetcore.docs: what is different with RewriteMiddleware

[infofromca]

use RewriteOptions.AddRedirectToHttps

---

Document Details

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

• ID: c7ddfb2f-5dea-5e31-2a27-02a4dc16104c
• Version Independent ID: 12ca0b9a-2638-a4ce-c45f-d4579c83dafb
• Content: Enforce HTTPS in ASP.NET Core
• Content Source: aspnetcore/security/enforcing-ssl.md
• Product: asp.net-core
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

Are you asking why AddRedirectToHttps is not used in place of app.UseHttpsRedirection(); ?

[Rick-Anderson]

URL redirect to a secure endpoint uses AddRedirectToHttps

@Tratcher should that be updated to recommend app.UseHttpsRedirection(); ?
Why is app.UseHttpsRedirection(); used rather than RewriteOptions.AddRedirectToHttps ?

[guardrex]

~You can set the status code and port with the URL Rewriting Middleware.~ Not the diff ... I noticed the new options on redirect middleware DO allow setting the status code and port. It's just that the URL Rewriting Middleware can handle additional redirect rules.

We already have this note in the URL Rewriting Middleware topic ...

When redirecting to HTTPS on port 443 without the requirement for additional redirect rules, we recommend using HTTPS Redirection Middleware. For more information, see the Enforce HTTPS topic.

[guardrex]

@Rick-Anderson How about a reverse note ... link from this topic (Enforce HTTPS) out to the URL Rewriting Middleware topic that says 'if you need to set the status code or status code and port, use the rewriting middleware.'

[Rick-Anderson]

@guardrex fantastic idea.

[guardrex]

Sure ... piece of :cake: