52 KiB

Raw Blame History

title

author

description

monikerRange

ms.author

ms.custom

ms.date

no-loc

uid

Response compression in ASP.NET Core

rick-anderson

Learn about response compression and how to use Response Compression Middleware in ASP.NET Core apps.

>= aspnetcore-2.1

riande

mvc

02/07/2020

appsettings.json

ASP.NET Core Identity

Blazor

Blazor Server

Blazor WebAssembly

Identity

Let's Encrypt

Razor

SignalR

performance/response-compression

Response compression in ASP.NET Core

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

Network bandwidth is a limited resource. Reducing the size of the response usually increases the responsiveness of an app, often dramatically. One way to reduce payload sizes is to compress an app's responses.

View or download sample code (how to download)

When to use Response Compression Middleware

Use server-based response compression technologies in IIS, Apache, or Nginx. The performance of the middleware probably won't match that of the server modules. HTTP.sys server server and Kestrel server don't currently offer built-in compression support.

Use Response Compression Middleware when you're:

Unable to use the following server-based compression technologies:
Hosting directly on:
- HTTP.sys server (formerly called WebListener)
- Kestrel server

Response compression

Usually, any response not natively compressed can benefit from response compression. Responses not natively compressed typically include: CSS, JavaScript, HTML, XML, and JSON. You shouldn't compress natively compressed assets, such as PNG files. If you attempt to further compress a natively compressed response, any small additional reduction in size and transmission time will likely be overshadowed by the time it took to process the compression. Don't compress files smaller than about 150-1000 bytes (depending on the file's content and the efficiency of compression). The overhead of compressing small files may produce a compressed file larger than the uncompressed file.

When a client can process compressed content, the client must inform the server of its capabilities by sending the Accept-Encoding header with the request. When a server sends compressed content, it must include information in the Content-Encoding header on how the compressed response is encoded. Content encoding designations supported by the middleware are shown in the following table.

`Accept-Encoding` header values	Middleware Supported	Description
`br`	Yes (default)	Brotli compressed data format
`deflate`	No	DEFLATE compressed data format
`exi`	No	W3C Efficient XML Interchange
`gzip`	Yes	Gzip file format
`identity`	Yes	"No encoding" identifier: The response must not be encoded.
`pack200-gzip`	No	Network Transfer Format for Java Archives
`*`	Yes	Any available content encoding not explicitly requested

For more information, see the IANA Official Content Coding List.

The middleware allows you to add additional compression providers for custom Accept-Encoding header values. For more information, see Custom Providers below.

The middleware is capable of reacting to quality value (qvalue, q) weighting when sent by the client to prioritize compression schemes. For more information, see RFC 7231: Accept-Encoding.

Compression algorithms are subject to a tradeoff between compression speed and the effectiveness of the compression. Effectiveness in this context refers to the size of the output after compression. The smallest size is achieved by the most optimal compression.

The headers involved in requesting, sending, caching, and receiving compressed content are described in the table below.

Header	Role
`Accept-Encoding`	Sent from the client to the server to indicate the content encoding schemes acceptable to the client.
`Content-Encoding`	Sent from the server to the client to indicate the encoding of the content in the payload.
`Content-Length`	When compression occurs, the `Content-Length` header is removed, since the body content changes when the response is compressed.
`Content-MD5`	When compression occurs, the `Content-MD5` header is removed, since the body content has changed and the hash is no longer valid.
`Content-Type`	Specifies the MIME type of the content. Every response should specify its `Content-Type`. The middleware checks this value to determine if the response should be compressed. The middleware specifies a set of default MIME types that it can encode, but you can replace or add MIME types.
`Vary`	When sent by the server with a value of `Accept-Encoding` to clients and proxies, the `Vary` header indicates to the client or proxy that it should cache (vary) responses based on the value of the `Accept-Encoding` header of the request. The result of returning content with the `Vary: Accept-Encoding` header is that both compressed and uncompressed responses are cached separately.

Explore the features of the Response Compression Middleware with the sample app. The sample illustrates:

The compression of app responses using Gzip and custom compression providers.
How to add a MIME type to the default list of MIME types for compression.

Package

Response Compression Middleware is provided by the Microsoft.AspNetCore.ResponseCompression package, which is implicitly included in ASP.NET Core apps.

Configuration

The following code shows how to enable the Response Compression Middleware for default MIME types and compression providers (Brotli and Gzip):

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddResponseCompression();
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app.UseResponseCompression();
    }
}

Notes:

app.UseResponseCompression must be called before any middleware that compresses responses. For more information, see xref:fundamentals/middleware/index#middleware-order.
Use a tool such as Fiddler, Firebug, or Postman to set the Accept-Encoding request header and study the response headers, size, and body.

Submit a request to the sample app without the Accept-Encoding header and observe that the response is uncompressed. The Content-Encoding and Vary headers aren't present on the response.

Submit a request to the sample app with the Accept-Encoding: br header (Brotli compression) and observe that the response is compressed. The Content-Encoding and Vary headers are present on the response.

Providers

Brotli Compression Provider

Use the xref:Microsoft.AspNetCore.ResponseCompression.BrotliCompressionProvider to compress responses with the Brotli compressed data format.

If no compression providers are explicitly added to the xref:Microsoft.AspNetCore.ResponseCompression.CompressionProviderCollection:

The Brotli Compression Provider is added by default to the array of compression providers along with the Gzip compression provider.
Compression defaults to Brotli compression when the Brotli compressed data format is supported by the client. If Brotli isn't supported by the client, compression defaults to Gzip when the client supports Gzip compression.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();
}

The Brotli Compression Provider must be added when any compression providers are explicitly added:

[!code-csharp]

Set the compression level with xref:Microsoft.AspNetCore.ResponseCompression.BrotliCompressionProviderOptions. The Brotli Compression Provider defaults to the fastest compression level (CompressionLevel.Fastest), which might not produce the most efficient compression. If the most efficient compression is desired, configure the middleware for optimal compression.

Compression Level	Description
CompressionLevel.Fastest	Compression should complete as quickly as possible, even if the resulting output isn't optimally compressed.
CompressionLevel.NoCompression	No compression should be performed.
CompressionLevel.Optimal	Responses should be optimally compressed, even if the compression takes more time to complete.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();

    services.Configure<BrotliCompressionProviderOptions>(options => 
    {
        options.Level = CompressionLevel.Fastest;
    });
}

Gzip Compression Provider

Use the xref:Microsoft.AspNetCore.ResponseCompression.GzipCompressionProvider to compress responses with the Gzip file format.

If no compression providers are explicitly added to the xref:Microsoft.AspNetCore.ResponseCompression.CompressionProviderCollection:

The Gzip Compression Provider is added by default to the array of compression providers along with the Brotli Compression Provider.
Compression defaults to Brotli compression when the Brotli compressed data format is supported by the client. If Brotli isn't supported by the client, compression defaults to Gzip when the client supports Gzip compression.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();
}

The Gzip Compression Provider must be added when any compression providers are explicitly added:

[!code-csharp]

Set the compression level with xref:Microsoft.AspNetCore.ResponseCompression.GzipCompressionProviderOptions. The Gzip Compression Provider defaults to the fastest compression level (CompressionLevel.Fastest), which might not produce the most efficient compression. If the most efficient compression is desired, configure the middleware for optimal compression.

Compression Level	Description
CompressionLevel.Fastest	Compression should complete as quickly as possible, even if the resulting output isn't optimally compressed.
CompressionLevel.NoCompression	No compression should be performed.
CompressionLevel.Optimal	Responses should be optimally compressed, even if the compression takes more time to complete.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();

    services.Configure<GzipCompressionProviderOptions>(options => 
    {
        options.Level = CompressionLevel.Fastest;
    });
}

Custom providers

Create custom compression implementations with xref:Microsoft.AspNetCore.ResponseCompression.ICompressionProvider. The xref:Microsoft.AspNetCore.ResponseCompression.ICompressionProvider.EncodingName* represents the content encoding that this ICompressionProvider produces. The middleware uses this information to choose the provider based on the list specified in the Accept-Encoding header of the request.

Using the sample app, the client submits a request with the Accept-Encoding: mycustomcompression header. The middleware uses the custom compression implementation and returns the response with a Content-Encoding: mycustomcompression header. The client must be able to decompress the custom encoding in order for a custom compression implementation to work.

[!code-csharp]

Submit a request to the sample app with the Accept-Encoding: mycustomcompression header and observe the response headers. The Vary and Content-Encoding headers are present on the response. The response body (not shown) isn't compressed by the sample. There isn't a compression implementation in the CustomCompressionProvider class of the sample. However, the sample shows where you would implement such a compression algorithm.

MIME types

The middleware specifies a default set of MIME types for compression:

application/javascript
application/json
application/xml
text/css
text/html
text/json
text/plain
text/xml

Replace or append MIME types with the Response Compression Middleware options. Note that wildcard MIME types, such as text/* aren't supported. The sample app adds a MIME type for image/svg+xml and compresses and serves the ASP.NET Core banner image (banner.svg).

[!code-csharp]

Compression with secure protocol

Compressed responses over secure connections can be controlled with the EnableForHttps option, which is disabled by default. Using compression with dynamically generated pages can lead to security problems such as the CRIME and BREACH attacks.

Adding the Vary header

When compressing responses based on the Accept-Encoding header, there are potentially multiple compressed versions of the response and an uncompressed version. In order to instruct client and proxy caches that multiple versions exist and should be stored, the Vary header is added with an Accept-Encoding value. In ASP.NET Core 2.0 or later, the middleware adds the Vary header automatically when the response is compressed.

Middleware issue when behind an Nginx reverse proxy

When a request is proxied by Nginx, the Accept-Encoding header is removed. Removal of the Accept-Encoding header prevents the middleware from compressing the response. For more information, see NGINX: Compression and Decompression. This issue is tracked by Figure out pass-through compression for Nginx (aspnet/BasicMiddleware #123).

Working with IIS dynamic compression

If you have an active IIS Dynamic Compression Module configured at the server level that you would like to disable for an app, disable the module with an addition to the web.config file. For more information, see Disabling IIS modules.

Troubleshooting

Use a tool like Fiddler, Firebug, or Postman, which allow you to set the Accept-Encoding request header and study the response headers, size, and body. By default, Response Compression Middleware compresses responses that meet the following conditions:

The Accept-Encoding header is present with a value of br, gzip, *, or custom encoding that matches a custom compression provider that you've established. The value must not be identity or have a quality value (qvalue, q) setting of 0 (zero).
The MIME type (Content-Type) must be set and must match a MIME type configured on the xref:Microsoft.AspNetCore.ResponseCompression.ResponseCompressionOptions.
The request must not include the Content-Range header.
The request must use insecure protocol (http), unless secure protocol (https) is configured in the Response Compression Middleware options. Note the danger described above when enabling secure content compression.

Additional resources

::: moniker-end

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

View or download sample code (how to download)

When to use Response Compression Middleware

Use Response Compression Middleware when you're:

Unable to use the following server-based compression technologies:
Hosting directly on:
- HTTP.sys server (formerly called WebListener)
- Kestrel server

Response compression

`Accept-Encoding` header values	Middleware Supported	Description
`br`	Yes (default)	Brotli compressed data format
`deflate`	No	DEFLATE compressed data format
`exi`	No	W3C Efficient XML Interchange
`gzip`	Yes	Gzip file format
`identity`	Yes	"No encoding" identifier: The response must not be encoded.
`pack200-gzip`	No	Network Transfer Format for Java Archives
`*`	Yes	Any available content encoding not explicitly requested

For more information, see the IANA Official Content Coding List.

The middleware allows you to add additional compression providers for custom Accept-Encoding header values. For more information, see Custom Providers below.

The middleware is capable of reacting to quality value (qvalue, q) weighting when sent by the client to prioritize compression schemes. For more information, see RFC 7231: Accept-Encoding.

The headers involved in requesting, sending, caching, and receiving compressed content are described in the table below.

Header	Role
`Accept-Encoding`	Sent from the client to the server to indicate the content encoding schemes acceptable to the client.
`Content-Encoding`	Sent from the server to the client to indicate the encoding of the content in the payload.
`Content-Length`	When compression occurs, the `Content-Length` header is removed, since the body content changes when the response is compressed.
`Content-MD5`	When compression occurs, the `Content-MD5` header is removed, since the body content has changed and the hash is no longer valid.
`Content-Type`	Specifies the MIME type of the content. Every response should specify its `Content-Type`. The middleware checks this value to determine if the response should be compressed. The middleware specifies a set of default MIME types that it can encode, but you can replace or add MIME types.
`Vary`	When sent by the server with a value of `Accept-Encoding` to clients and proxies, the `Vary` header indicates to the client or proxy that it should cache (vary) responses based on the value of the `Accept-Encoding` header of the request. The result of returning content with the `Vary: Accept-Encoding` header is that both compressed and uncompressed responses are cached separately.

Explore the features of the Response Compression Middleware with the sample app. The sample illustrates:

The compression of app responses using Gzip and custom compression providers.
How to add a MIME type to the default list of MIME types for compression.

Package

To include the middleware in a project, add a reference to the Microsoft.AspNetCore.App metapackage, which includes the Microsoft.AspNetCore.ResponseCompression package.

Configuration

The following code shows how to enable the Response Compression Middleware for default MIME types and compression providers (Brotli and Gzip):

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddResponseCompression();
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app.UseResponseCompression();
    }
}

Notes:

app.UseResponseCompression must be called before any middleware that compresses responses. For more information, see xref:fundamentals/middleware/index#middleware-order.
Use a tool such as Fiddler, Firebug, or Postman to set the Accept-Encoding request header and study the response headers, size, and body.

Submit a request to the sample app without the Accept-Encoding header and observe that the response is uncompressed. The Content-Encoding and Vary headers aren't present on the response.

Providers

Brotli Compression Provider

Use the xref:Microsoft.AspNetCore.ResponseCompression.BrotliCompressionProvider to compress responses with the Brotli compressed data format.

If no compression providers are explicitly added to the xref:Microsoft.AspNetCore.ResponseCompression.CompressionProviderCollection:

The Brotli Compression Provider is added by default to the array of compression providers along with the Gzip compression provider.
Compression defaults to Brotli compression when the Brotli compressed data format is supported by the client. If Brotli isn't supported by the client, compression defaults to Gzip when the client supports Gzip compression.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();
}

The Brotli Compression Provider must be added when any compression providers are explicitly added:

[!code-csharp]

Compression Level	Description
CompressionLevel.Fastest	Compression should complete as quickly as possible, even if the resulting output isn't optimally compressed.
CompressionLevel.NoCompression	No compression should be performed.
CompressionLevel.Optimal	Responses should be optimally compressed, even if the compression takes more time to complete.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();

    services.Configure<BrotliCompressionProviderOptions>(options => 
    {
        options.Level = CompressionLevel.Fastest;
    });
}

Gzip Compression Provider

Use the xref:Microsoft.AspNetCore.ResponseCompression.GzipCompressionProvider to compress responses with the Gzip file format.

If no compression providers are explicitly added to the xref:Microsoft.AspNetCore.ResponseCompression.CompressionProviderCollection:

The Gzip Compression Provider is added by default to the array of compression providers along with the Brotli Compression Provider.
Compression defaults to Brotli compression when the Brotli compressed data format is supported by the client. If Brotli isn't supported by the client, compression defaults to Gzip when the client supports Gzip compression.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();
}

The Gzip Compression Provider must be added when any compression providers are explicitly added:

[!code-csharp]

Compression Level	Description
CompressionLevel.Fastest	Compression should complete as quickly as possible, even if the resulting output isn't optimally compressed.
CompressionLevel.NoCompression	No compression should be performed.
CompressionLevel.Optimal	Responses should be optimally compressed, even if the compression takes more time to complete.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();

    services.Configure<GzipCompressionProviderOptions>(options => 
    {
        options.Level = CompressionLevel.Fastest;
    });
}

Custom providers

[!code-csharp]

MIME types

The middleware specifies a default set of MIME types for compression:

application/javascript
application/json
application/xml
text/css
text/html
text/json
text/plain
text/xml

[!code-csharp]

Compression with secure protocol

Adding the Vary header

Middleware issue when behind an Nginx reverse proxy

Working with IIS dynamic compression

Troubleshooting

The Accept-Encoding header is present with a value of br, gzip, *, or custom encoding that matches a custom compression provider that you've established. The value must not be identity or have a quality value (qvalue, q) setting of 0 (zero).
The MIME type (Content-Type) must be set and must match a MIME type configured on the xref:Microsoft.AspNetCore.ResponseCompression.ResponseCompressionOptions.
The request must not include the Content-Range header.
The request must use insecure protocol (http), unless secure protocol (https) is configured in the Response Compression Middleware options. Note the danger described above when enabling secure content compression.

Additional resources

::: moniker-end

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

View or download sample code (how to download)

When to use Response Compression Middleware

Use Response Compression Middleware when you're:

Unable to use the following server-based compression technologies:
Hosting directly on:
- HTTP.sys server (formerly called WebListener)
- Kestrel server

Response compression

`Accept-Encoding` header values	Middleware Supported	Description
`br`	No	Brotli compressed data format
`deflate`	No	DEFLATE compressed data format
`exi`	No	W3C Efficient XML Interchange
`gzip`	Yes (default)	Gzip file format
`identity`	Yes	"No encoding" identifier: The response must not be encoded.
`pack200-gzip`	No	Network Transfer Format for Java Archives
`*`	Yes	Any available content encoding not explicitly requested

For more information, see the IANA Official Content Coding List.

The middleware allows you to add additional compression providers for custom Accept-Encoding header values. For more information, see Custom Providers below.

The middleware is capable of reacting to quality value (qvalue, q) weighting when sent by the client to prioritize compression schemes. For more information, see RFC 7231: Accept-Encoding.

The headers involved in requesting, sending, caching, and receiving compressed content are described in the table below.

Header	Role
`Accept-Encoding`	Sent from the client to the server to indicate the content encoding schemes acceptable to the client.
`Content-Encoding`	Sent from the server to the client to indicate the encoding of the content in the payload.
`Content-Length`	When compression occurs, the `Content-Length` header is removed, since the body content changes when the response is compressed.
`Content-MD5`	When compression occurs, the `Content-MD5` header is removed, since the body content has changed and the hash is no longer valid.
`Content-Type`	Specifies the MIME type of the content. Every response should specify its `Content-Type`. The middleware checks this value to determine if the response should be compressed. The middleware specifies a set of default MIME types that it can encode, but you can replace or add MIME types.
`Vary`	When sent by the server with a value of `Accept-Encoding` to clients and proxies, the `Vary` header indicates to the client or proxy that it should cache (vary) responses based on the value of the `Accept-Encoding` header of the request. The result of returning content with the `Vary: Accept-Encoding` header is that both compressed and uncompressed responses are cached separately.

Explore the features of the Response Compression Middleware with the sample app. The sample illustrates:

The compression of app responses using Gzip and custom compression providers.
How to add a MIME type to the default list of MIME types for compression.

Package

To include the middleware in a project, add a reference to the Microsoft.AspNetCore.App metapackage, which includes the Microsoft.AspNetCore.ResponseCompression package.

Configuration

The following code shows how to enable the Response Compression Middleware for default MIME types and the Gzip Compression Provider:

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddResponseCompression();
    }

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        app.UseResponseCompression();
    }
}

Notes:

app.UseResponseCompression must be called before any middleware that compresses responses. For more information, see xref:fundamentals/middleware/index#middleware-order.
Use a tool such as Fiddler, Firebug, or Postman to set the Accept-Encoding request header and study the response headers, size, and body.

Submit a request to the sample app without the Accept-Encoding header and observe that the response is uncompressed. The Content-Encoding and Vary headers aren't present on the response.

Submit a request to the sample app with the Accept-Encoding: gzip header and observe that the response is compressed. The Content-Encoding and Vary headers are present on the response.

Providers

Gzip Compression Provider

Use the xref:Microsoft.AspNetCore.ResponseCompression.GzipCompressionProvider to compress responses with the Gzip file format.

If no compression providers are explicitly added to the xref:Microsoft.AspNetCore.ResponseCompression.CompressionProviderCollection:

The Gzip Compression Provider is added by default to the array of compression providers.
Compression defaults to Gzip when the client supports Gzip compression.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();
}

The Gzip Compression Provider must be added when any compression providers are explicitly added:

[!code-csharp]

Compression Level	Description
CompressionLevel.Fastest	Compression should complete as quickly as possible, even if the resulting output isn't optimally compressed.
CompressionLevel.NoCompression	No compression should be performed.
CompressionLevel.Optimal	Responses should be optimally compressed, even if the compression takes more time to complete.

public void ConfigureServices(IServiceCollection services)
{
    services.AddResponseCompression();

    services.Configure<GzipCompressionProviderOptions>(options => 
    {
        options.Level = CompressionLevel.Fastest;
    });
}

Custom providers

[!code-csharp]

MIME types

The middleware specifies a default set of MIME types for compression:

application/javascript
application/json
application/xml
text/css
text/html
text/json
text/plain
text/xml

[!code-csharp]

Compression with secure protocol

Adding the Vary header

Middleware issue when behind an Nginx reverse proxy

Working with IIS dynamic compression

Troubleshooting

The Accept-Encoding header is present with a value of gzip, *, or custom encoding that matches a custom compression provider that you've established. The value must not be identity or have a quality value (qvalue, q) setting of 0 (zero).
The MIME type (Content-Type) must be set and must match a MIME type configured on the xref:Microsoft.AspNetCore.ResponseCompression.ResponseCompressionOptions.
The request must not include the Content-Range header.
The request must use insecure protocol (http), unless secure protocol (https) is configured in the Response Compression Middleware options. Note the danger described above when enabling secure content compression.

Additional resources

::: moniker-end

52 KiB Raw Blame History

Response compression in ASP.NET Core

When to use Response Compression Middleware

Response compression

Package

Configuration

Providers

Brotli Compression Provider

Gzip Compression Provider

Custom providers

MIME types

Compression with secure protocol

Adding the Vary header

Middleware issue when behind an Nginx reverse proxy

Working with IIS dynamic compression

Troubleshooting

Additional resources

When to use Response Compression Middleware

Response compression

Package

Configuration

Providers

Brotli Compression Provider

Gzip Compression Provider

Custom providers

MIME types

Compression with secure protocol

Adding the Vary header

Middleware issue when behind an Nginx reverse proxy

Working with IIS dynamic compression

Troubleshooting

Additional resources

When to use Response Compression Middleware

Response compression

Package

Configuration

Providers

Gzip Compression Provider

Custom providers

MIME types

Compression with secure protocol

Adding the Vary header

Middleware issue when behind an Nginx reverse proxy

Working with IIS dynamic compression

Troubleshooting

Additional resources

52 KiB

Raw Blame History