daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Prep for 8.0 version (#28649)

pull/28652/head
Tom Dykstra 2023-03-10 14:33:54 -08:00 committed by GitHub
parent 5c2c2e6f16
commit 3250cabe2f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 1929 additions and 1358 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1379
aspnetcore/fundamentals/servers/kestrel/endpoints.md
View File

File diff suppressed because it is too large Load Diff

1894
aspnetcore/fundamentals/servers/kestrel/endpoints/includes/endpoints5-7.md 100644
View File

File diff suppressed because it is too large Load Diff

14
aspnetcore/includes/http-ports 100644
View File

@ -0,0 +1,14 @@
Apps and containers are often given only a port to listen on, like port 80, without additional constraints like host or path. HTTP_PORTS and HTTPS_PORTS are config keys that specify the listening ports for the Kestrel and HttpSys servers. These may be specified as environment variables defined with the `DOTNET_` or `ASPNETCORE_` prefixes, or specified directly through any other config input, such as `appsettings.json`. Each is a semicolon-delimited list of port values, as shown in the following example:
```
ASPNETCORE_HTTP_PORTS=80;8080
ASPNETCORE_HTTPS_PORTS=443;8081
```
The preceding example is shorthand for the following configuration, which specifies the scheme (HTTP or HTTPS) and any host or IP.
```
ASPNETCORE_URLS=http://*:80/;http://*:8080/;https://*:443/;https://*:8081/
```
The HTTP_PORTS and HTTPS_PORTS configuration keys are lower priority and are overridden by URLS or values provided directly in code. Certificates still need to be configured separately via server-specific mechanics for HTTPS.