Https redirection doc page is absolutely confusing, no clear advice

[DevTKSS]

Before you open an issue

If the issue is with an ASP.NET Core document:

• Do not open a new issue using this form.

😅 Then you should fix the choosen "Doc Issue" issue template to work on mobile?

• Open the issue using the Open a documentation issue link and feedback form at the bottom of the article.

Using the Open a documentation issue link and form to open an issue adds article metadata for tracking, which indicates the article that you're commenting on.

Page with problem: https://learn.microsoft.com/de-de/aspnet/core/security/enforcing-ssl?view=aspnetcore-9.0&tabs=visual-studio%2Clinux-sles

If the issue is:

• A simple typo or similar correction, you can submit a PR. See the Contributor Guide for instructions: https://docs.microsoft.com/contribute/#quick-edits-to-existing-documents
• A general support question, consider asking on a support forum:
  • Stack Overflow: https://stackoverflow.com/questions/tagged/asp.net-core
  • ASP.NET Core Slack: https://aspnetcore.slack.com/join/shared_invite/zt-1mv5487zb-EOZxJ1iqb0A0ajowEbxByQ#/shared-invite/email
  • ASP.NET Gitter: https://gitter.im/aspnet/Home
• A site design concern, create an issue at MicrosoftDocs/Feedback: https://github.com/MicrosoftDocs/Feedback/issues/new/choose
• A problem completing a tutorial, compare your code with the completed sample.
• A duplicate of an open or closed issue, leave a comment on that issue.

Issue description

The documentation article is constantly switching between the advised way to do this and somehow it seems to me, that the content is duplicated? Just on mobile device right now.

I would read the first paragraph as if we should not use app.UseHttpsRedirection() in production then this Htst (sorry if misspelled) encapsulated for production usage, which would make me assume as reader this would be a if-else (not just 2 seperate if blocks just with one negated and one not)?
Then its telling how to set Htst up with is primary good, but then the next section again advises us to use that other method?! Absolutely confused now 🫣

I would like to set this up correctly so I would not get the known cors / antiforgery header issues for a WebAssembly dotnet/runtime using app + use https, and was advised to use this article page😅🤷

Software versions

Check the .NET target framework(s) being used, and include the version number(s).

• .NET Core
• .NET 5.0 or later
• .NET Framework
• .NET Standard

If using the .NET Core SDK, include dotnet --info output. If using .NET Framework without the .NET Core SDK, include info from Visual Studio's Help > About Microsoft Visual Studio dialog.

dotnet --info output or About VS info

<replace>

[guardrex]

Hi @DevTKSS ... Would you open this from the bottom of the article using the Open a documentation issue link? That will add the correct metadata and ping the author of the article automatically. If it turns out to be Rick, who is retired, one of us will assist with it.

[guardrex]

Then you should fix the choosen "Doc Issue" issue template to work on mobile?

I just opened an issue from my phone (Chrome on Android), and it works here ...

#35787

We request that readers use the "Open a documentation issue" link/form process because we're slammed with work most of the time and would like to have the metadata and pings automated.

[DevTKSS]

@guardrex I did exactly the same, no idea, but yes of course I would absolutly agree for the automation purposes! Dont know why it does not work on my device. are there plans or issues to follow up or provide information to get this fixed in the future? could think of, me beeing not the only person having this strange behavior...

[guardrex]

Follow this guidance to open an internal issue for them that the link/form isn't working ...

https://learn.microsoft.com/contribute/content/provide-feedback#use-the-standard-experience

Let them know what OS and browser you're using.

[DevTKSS]

@guardrex will do tomorrow, here its quite late now. But thanks for your help!

[guardrex]

If you can't get this issue re-opened from the article, let me know here. I'll manually inject the metadata.

[DevTKSS]

@guardrex I tryed to add a "Give Product Feedback" link using feedback like you mentioned and linked, but by using the second bottom link:

this is ONLY directing me to aspnetcore/CONTRIBUTING.md file, instead of a Feedback Form 🤔 could you maybe tell, if this is wanted this way? I mean, normally if someone asks for giving feedback my first assumption would not be, that I suggest this person to kind of "well then do it yourself!" 😆

[guardrex]

That feedback link (of the two there) is primarily to provide feedback about the framework to the product unit, and that's the correct landing page for them in the dotnet/aspnetcore repo. The relevant section is Bugs and feature requests?. Then, they want people to provide the feedback for one of the choices listed there by opening an issue. There's been no problem with this approach over the years as far as I know.

[DevTKSS]

@guardrex okay, so for the from you mentioned mobile device to open an issue but which did not add your desired metadata like as it does fine using chrome with desktop browser with that first link or to suggest for example (which I was targeting right now to ask them) that the api docs should have a redirect to the appropriate how to docs like I know it form vb.net winforms framework articles, of... e.g. how to set up a Table with rows and columns that past days, but now for example with net 8+ I moved to with c# I am having a hard time finding those articles that are telling not only the implementation, then also some sample code etc like we have in the asp net core docs 👍 For this kind of feedback to improve or fix things, I would search that form I seem to miss. Is that done via that thump Feedback thing or...? Sorry for "dump" questions if those are, I just did not find this answer until now 😅

[guardrex]

the api docs should have a redirect to the appropriate how to docs

Feedback for the API Browser goes here ...

https://github.com/dotnet/dotnet-api-docs/issues