Fixes#9549
* Not a full UE pass on the group of external provider topics ... don't quite have time for that right now. However, I do hit a number of small UE-type updates.
* Engineering: You only need to look at one thing here: See the *forwarded-headers-middleware.md* file. The content of the file is below. The INCLUDE is linked into the external auth provider topics to surface Forwarded Headers Middleware (proxy/LB topic).
> \#\# Forward request information with a proxy or load balancer
>
> If the app is deployed behind a proxy server or load balancer, some of the original request information might be forwarded to the app in request headers. This information usually includes the secure request scheme (\`https\`), host, and client IP address. Apps don't automatically read these request headers to discover and use the original request information.
>
> The scheme is used in link generation that affects the authentication flow with external providers. Losing the secure scheme (\`https\`) results in the app generating incorrect insecure redirect URLs.
>
> Use Forwarded Headers Middleware to make the original request information available to the app for request processing.
>
> For more information, see \<xref:host-and-deploy/proxy-load-balancer>.
If it's easier to provide feedback in a comment here over hunting down the file on the diff, that works for me.
I spent a day or more researching this so that I could use Swagger-UI in my ASP.NET Core API which is used with a reverse-proxy and virtual directory. In the end found Swagger-UI requires relative URLs to start with a period. Related to https://github.com/swagger-api/swagger-ui/issues/4107
Hoping this documentation note will help others.
When creating a new PR, please do the following and delete this template text:
* Reference the issue number if there is one:
Fixes #Issue_Number
> The "Fixes #nnn" syntax in the PR description causes
> GitHub to automatically close the issue when this PR is merged.
* Add docs for api conventions and analyzers
Fixes#8332
* Edit pass on API conventions and analyzers content (#9574)
* Edit pass on 2.2 API docs (#9578)
* Scottaddie/open api patch (#9582)
* Edit pass on 2.2 API docs
* Resolve build warning
* Fix list formatting
This addresses the issue #9557 that I was working on with @scottaddie.
Unfortunately, I experienced severe GitHub workflow issues, and the pull request was closed.
Fixes#9470
[Internal Review Topic (How to download a sample section)](https://review.docs.microsoft.com/en-us/aspnet/core/index?view=aspnetcore-1.0&branch=pr-en-us-9544#how-to-download-a-sample)
I'm not very trusting of ✨ *Magic Build Systems* ✨. I usually encode reserved DocFX characters outside of code-fenced content ... *they'll **never** break this way no matter what the build system thinks about them*.
If you prefer that I go with either a backslash (safe) or roll the 🎲🎲 and use unencoded chars with build system processing trust, let me know which alternate way you would like to go. Again, my approach is **_bulletproof_**.
Thanks @rswetnam! 🚀
Making it a bit clearer that the [controller] name replacement of MyNameController is by naming convention.
<!--
When creating a new PR, please do the following:
* Reference the issue number if there is one, e.g.:
Fixes #Issue_Number
The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
NOTE: This is a comment; please type your descriptions above or below it.
-->
<!--
When creating a new PR, please do the following:
* Reference the issue number if there is one, e.g.:
Fixes #Issue_Number
The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
NOTE: This is a comment; please type your descriptions above or below it.
-->
More for #9441 with a bit of refactoring.
- IISServerOptions (inproc) are unique from IISOptions (out of proc)
- Move HTTP/2 topic lower in the document (flow felt off by having it before how to enable IISIntegration)
- Remove stop/starting app pool in favor of dropping app_offline (@shirhatti for thoughts)
- Generalize addressing AspNetCore behind IIS (remove reverse proxy stuff).