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

18 KiB
Raw Blame History

title author description monikerRange ms.author ms.custom ms.date uid
HTTP.sys web server implementation in ASP.NET Core guardrex Learn about HTTP.sys, a web server for ASP.NET Core on Windows. Built on the HTTP.sys kernel-mode driver, HTTP.sys is an alternative to Kestrel that can be used for direct connection to the Internet without IIS. >= aspnetcore-2.0 tdykstra mvc 02/21/2019 fundamentals/servers/httpsys

HTTP.sys web server implementation in ASP.NET Core

By Tom Dykstra, Chris Ross, and Luke Latham

HTTP.sys is a web server for ASP.NET Core that only runs on Windows. HTTP.sys is an alternative to Kestrel server and offers some features that Kestrel doesn't provide.

[!IMPORTANT] HTTP.sys isn't compatible with the ASP.NET Core Module and can't be used with IIS or IIS Express.

HTTP.sys supports the following features:

  • Windows Authentication
  • Port sharing
  • HTTPS with SNI
  • HTTP/2 over TLS (Windows 10 or later)
  • Direct file transmission
  • Response caching
  • WebSockets (Windows 8 or later)

Supported Windows versions:

  • Windows 7 or later
  • Windows Server 2008 R2 or later

View or download sample code (how to download)

When to use HTTP.sys

HTTP.sys is useful for deployments where:

  • There's a need to expose the server directly to the Internet without using IIS.

    HTTP.sys communicates directly with the Internet

  • An internal deployment requires a feature not available in Kestrel, such as Windows Authentication.

    HTTP.sys communicates directly with the internal network

HTTP.sys is mature technology that protects against many types of attacks and provides the robustness, security, and scalability of a full-featured web server. IIS itself runs as an HTTP listener on top of HTTP.sys.

HTTP/2 support

HTTP/2 is enabled for ASP.NET Core apps if the following base requirements are met:

::: moniker range=">= aspnetcore-2.2"

If an HTTP/2 connection is established, HttpRequest.Protocol reports HTTP/2.

::: moniker-end

::: moniker range="< aspnetcore-2.2"

If an HTTP/2 connection is established, HttpRequest.Protocol reports HTTP/1.1.

::: moniker-end

HTTP/2 is enabled by default. If an HTTP/2 connection isn't established, the connection falls back to HTTP/1.1. In a future release of Windows, HTTP/2 configuration flags will be available, including the ability to disable HTTP/2 with HTTP.sys.

Kernel mode authentication with Kerberos

HTTP.sys delegates to kernel mode authentication with the Kerberos authentication protocol. User mode authentication isn't supported with Kerberos and HTTP.sys. The machine account must be used to decrypt the Kerberos token/ticket that's obtained from Active Directory and forwarded by the client to the server to authenticate the user. Register the Service Principal Name (SPN) for the host, not the user of the app.

How to use HTTP.sys

Configure the ASP.NET Core app to use HTTP.sys

  1. A package reference in the project file isn't required when using the Microsoft.AspNetCore.App metapackage (nuget.org) (ASP.NET Core 2.1 or later). When not using the Microsoft.AspNetCore.App metapackage, add a package reference to Microsoft.AspNetCore.Server.HttpSys.

  2. Call the xref:Microsoft.AspNetCore.Hosting.WebHostBuilderHttpSysExtensions.UseHttpSys* extension method when building Web Host, specifying any required xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions:

    [!code-csharp]

    Additional HTTP.sys configuration is handled through registry settings.

    HTTP.sys options

    Property Description Default
    AllowSynchronousIO Control whether synchronous input/output is allowed for the HttpContext.Request.Body and HttpContext.Response.Body. true
    Authentication.AllowAnonymous Allow anonymous requests. true
    Authentication.Schemes Specify the allowed authentication schemes. May be modified at any time prior to disposing the listener. Values are provided by the AuthenticationSchemes enum: Basic, Kerberos, Negotiate, None, and NTLM. None
    EnableResponseCaching Attempt kernel-mode caching for responses with eligible headers. The response may not include Set-Cookie, Vary, or Pragma headers. It must include a Cache-Control header that's public and either a shared-max-age or max-age value, or an Expires header. true
    xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.MaxAccepts The maximum number of concurrent accepts. 5 × Environment.
    ProcessorCount
    xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.MaxConnections The maximum number of concurrent connections to accept. Use -1 for infinite. Use null to use the registry's machine-wide setting. null
    (unlimited)
    xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.MaxRequestBodySize See the MaxRequestBodySize section. 30000000 bytes
    (~28.6 MB)
    xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.RequestQueueLimit The maximum number of requests that can be queued. 1000
    xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.ThrowWriteExceptions Indicate if response body writes that fail due to client disconnects should throw exceptions or complete normally. false
    (complete normally)
    xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.Timeouts Expose the HTTP.sys xref:Microsoft.AspNetCore.Server.HttpSys.TimeoutManager configuration, which may also be configured in the registry. Follow the API links to learn more about each setting, including default values:
    xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.UrlPrefixes Specify the xref:Microsoft.AspNetCore.Server.HttpSys.UrlPrefixCollection to register with HTTP.sys. The most useful is UrlPrefixCollection.Add, which is used to add a prefix to the collection. These may be modified at any time prior to disposing the listener.

    MaxRequestBodySize

    The maximum allowed size of any request body in bytes. When set to null, the maximum request body size is unlimited. This limit has no effect on upgraded connections, which are always unlimited.

    The recommended method to override the limit in an ASP.NET Core MVC app for a single IActionResult is to use the xref:Microsoft.AspNetCore.Mvc.RequestSizeLimitAttribute attribute on an action method:

    [RequestSizeLimit(100000000)]
public IActionResult MyActionMethod()

    An exception is thrown if the app attempts to configure the limit on a request after the app has started reading the request. An IsReadOnly property can be used to indicate if the MaxRequestBodySize property is in a read-only state, meaning it's too late to configure the limit.

    If the app should override xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.MaxRequestBodySize per-request, use the xref:Microsoft.AspNetCore.Http.Features.IHttpMaxRequestBodySizeFeature:

    [!code-csharp]

  3. If using Visual Studio, make sure the app isn't configured to run IIS or IIS Express.

    In Visual Studio, the default launch profile is for IIS Express. To run the project as a console app, manually change the selected profile, as shown in the following screen shot:

    Select console app profile

Configure Windows Server

  1. Determine the ports to open for the app and use Windows Firewall or the New-NetFirewallRule PowerShell cmdlet to open firewall ports to allow traffic to reach HTTP.sys. In the following commands and app configuration, port 443 is used.

  2. When deploying to an Azure VM, open the ports in the Network Security Group. In the following commands and app configuration, port 443 is used.

  3. Obtain and install X.509 certificates, if required.

    On Windows, create self-signed certificates using the New-SelfSignedCertificate PowerShell cmdlet. For an unsupported example, see UpdateIISExpressSSLForChrome.ps1.

    Install either self-signed or CA-signed certificates in the server's Local Machine > Personal store.

  4. If the app is a framework-dependent deployment, install .NET Core, .NET Framework, or both (if the app is a .NET Core app targeting the .NET Framework).

    • .NET Core – If the app requires .NET Core, obtain and run the .NET Core Runtime installer from .NET Core Downloads. Don't install the full SDK on the server.
    • .NET Framework – If the app requires .NET Framework, see the .NET Framework installation guide. Install the required .NET Framework. The installer for the latest .NET Framework is available from the .NET Core Downloads page.

    If the app is a self-contained deployment, the app includes the runtime in its deployment. No framework installation is required on the server.

  5. Configure URLs and ports in the app.

    By default, ASP.NET Core binds to http://localhost:5000. To configure URL prefixes and ports, options include:

    The following code example shows how to use xref:Microsoft.AspNetCore.Server.HttpSys.HttpSysOptions.UrlPrefixes with the server's local IP address 10.0.0.4 on port 443:

    [!code-csharp]

    An advantage of UrlPrefixes is that an error message is generated immediately for improperly formatted prefixes.

    The settings in UrlPrefixes override UseUrls/urls/ASPNETCORE_URLS settings. Therefore, an advantage of UseUrls, urls, and the ASPNETCORE_URLS environment variable is that it's easier to switch between Kestrel and HTTP.sys. For more information, see xref:fundamentals/host/web-host.

    HTTP.sys uses the HTTP Server API UrlPrefix string formats.

    [!WARNING] Top-level wildcard bindings (http://*:80/ and http://+:80) should not be used. Top-level wildcard bindings create app security vulnerabilities. This applies to both strong and weak wildcards. Use explicit host names or IP addresses rather than wildcards. Subdomain wildcard binding (for example, *.mysub.com) isn't a security risk if you control the entire parent domain (as opposed to *.com, which is vulnerable). For more information, see RFC 7230: Section 5.4: Host.

  6. Preregister URL prefixes on the server.

    The built-in tool for configuring HTTP.sys is netsh.exe. netsh.exe is used to reserve URL prefixes and assign X.509 certificates. The tool requires administrator privileges.

    Use the netsh.exe tool to register URLs for the app:

    netsh http add urlacl url=<URL> user=<USER>
    • <URL> – The fully qualified Uniform Resource Locator (URL). Don't use a wildcard binding. Use a valid hostname or local IP address. The URL must include a trailing slash.
    • <USER> – Specifies the user or user-group name.

    In the following example, the local IP address of the server is 10.0.0.4:

    netsh http add urlacl url=https://10.0.0.4:443/ user=Users

    When a URL is registered, the tool responds with URL reservation successfully added.

    To delete a registered URL, use the delete urlacl command:

    netsh http delete urlacl url=<URL>

  7. Register X.509 certificates on the server.

    Use the netsh.exe tool to register certificates for the app:

    netsh http add sslcert ipport=<IP>:<PORT> certhash=<THUMBPRINT> appid="{<GUID>}"
    • <IP> – Specifies the local IP address for the binding. Don't use a wildcard binding. Use a valid IP address.
    • <PORT> – Specifies the port for the binding.
    • <THUMBPRINT> – The X.509 certificate thumbprint.
    • <GUID> – A developer-generated GUID to represent the app for informational purposes.

    For reference purposes, store the GUID in the app as a package tag:

    • In Visual Studio:
      • Open the app's project properties by right-clicking on the app in Solution Explorer and selecting Properties.
      • Select the Package tab.
      • Enter the GUID that you created in the Tags field.
    • When not using Visual Studio:

      • Open the app's project file.

      • Add a <PackageTags> property to a new or existing <PropertyGroup> with the GUID that you created:

        <PropertyGroup>
  <PackageTags>9412ee86-c21b-4eb8-bd89-f650fbf44931</PackageTags>
</PropertyGroup>

    In the following example:

    • The local IP address of the server is 10.0.0.4.
    • An online random GUID generator provides the appid value.
    netsh http add sslcert 
    ipport=10.0.0.4:443 
    certhash=b66ee04419d4ee37464ab8785ff02449980eae10 
    appid="{9412ee86-c21b-4eb8-bd89-f650fbf44931}"

    When a certificate is registered, the tool responds with SSL Certificate successfully added.

    To delete a certificate registration, use the delete sslcert command:

    netsh http delete sslcert ipport=<IP>:<PORT>

    Reference documentation for netsh.exe:

  8. Run the app.

    Administrator privileges aren't required to run the app when binding to localhost using HTTP (not HTTPS) with a port number greater than 1024. For other configurations (for example, using a local IP address or binding to port 443), run the app with administrator privileges.

    The app responds at the server's public IP address. In this example, the server is reached from the Internet at its public IP address of 104.214.79.47.

    A development certificate is used in this example. The page loads securely after bypassing the browser's untrusted certificate warning.

    Browser window showing the app's Index page loaded

Proxy server and load balancer scenarios

For apps hosted by HTTP.sys that interact with requests from the Internet or a corporate network, additional configuration might be required when hosting behind proxy servers and load balancers. For more information, see Configure ASP.NET Core to work with proxy servers and load balancers.

Additional resources