Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HTTPS Redirection Middleware scoped to availability of HTTPS port #33611

Open
guardrex opened this issue Sep 16, 2024 · 0 comments · May be fixed by #33613
Open

HTTPS Redirection Middleware scoped to availability of HTTPS port #33611

guardrex opened this issue Sep 16, 2024 · 0 comments · May be fixed by #33613
Assignees
@guardrex
Labels
aspnet-core/svc doc-enhancement Pri1 High priority, do before Pri2 and Pri3

Comments

@guardrex
Copy link
Collaborator

Main doc set guidance doesn't mention that an HTTPS port has to be available for the middleware to take effect.

This issue came about as part of setting up the Blazor movie dB tutorial. I called it out there and figured it would be a good call-out for the main doc set. I'll sprinkle in a phrase to cover it.
@guardrex guardrex self-assigned this Sep 16, 2024
@guardrex guardrex added Pri1 High priority, do before Pri2 and Pri3 doc-enhancement and removed ⌚ Not Triaged labels Sep 16, 2024
@guardrex guardrex linked a pull request Sep 16, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guardrex guardrex

Labels
aspnet-core/svc doc-enhancement Pri1 High priority, do before Pri2 and Pri3
Projects
dotnet/AspNetCore.Docs September 2024 sprint
Status: 🏗 In progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Clarify middleware activation dotnet/AspNetCore.Docs
2 participants
@guardrex @dotnet-bot