CODEWITHSUNDEEP
c#asp.netasp.net-core.net-core
MindingData
MindingData

Reputation: 12508

GZIP in .net core not working

I'm attempting to add Gzip middleware to my ASP.net core app.

I have added the following package :

"Microsoft.AspNetCore.ResponseCompression": "1.0.0"

In my startup.cs for the Configure Services method I have the following : 

public void ConfigureServices(IServiceCollection services)
{
    services.Configure<GzipCompressionProviderOptions>(options => options.Level = CompressionLevel.Fastest);
    services.AddResponseCompression(options =>
    {
        options.Providers.Add<GzipCompressionProvider>();
    });

    services.AddMvc();
}

In my Configure method I have the following : 

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
{
    loggerFactory.AddConsole(Configuration.GetSection("Logging"));
    loggerFactory.AddDebug();

    app.UseResponseCompression();
    app.UseMvc();
}

However when I try and load a page, it doesn't come through as Gzip compressed. I have used both a string response and outputting a view. The response headers in chrome look like :

enter image description here

I am on a windows machine developing in visual studio. When running the app I have tried just running from Visual Studio (Via F5), and also using the "dotnet run" command from command line. Neither output GZip compression.

Upvotes: 35

Views: 24861

Answers (7)

Jim
Jim

Reputation: 509

Here is my solution:

  1. Make sure your Fiddler's "Decode" function is disabled. And you can see a yellow bar in the response. Disable Decode

  2. Or exit Fillder or other proxy app and have a try.

Upvotes: 0

Lion
Lion

Reputation: 17908

The answear from Mohammad Dayyan works great for compressing the HTML body. If you want to compress also static client files like CSS or JS, the Startup.Configure method must look like this: 

app.UseResponseCompression();
app.UseStaticFiles();

It's important to place app.UseResponseCompression() before app.UseStaticFiles(). Otherwise the static file handler sends the ressource to the client without applying any compression.

You can also add a black/or whitelist for mime types to compress in AddResponseCompression:

services.Configure<GzipCompressionProviderOptions>(options => options.Level = CompressionLevel.Fastest);
services.AddResponseCompression(options => {
    options.MimeTypes = new string[]{
        "text/html",
        "text/css",
        "application/javascript",
        "text/javascript"
        // ...
    };

    options.Providers.Add<GzipCompressionProvider>();
});

Excluding specific mime types is also possible due to the options.ExcludedMimeTypes property.

Yes, there are good arguments to keep such things seperated from the application server and use some reverse proxy for things like compression. This also allows the usage of the more effective Brotli algorithm in ASP.NET Core 2.1 LTS, which is officially only avaliable for the new 2.2 release (except custom middlewares relying on third party libraries).

This was also my first idea, but it seems that nginx 1.17.3 currently doesn't playing well with gzip and ASP.NET Core 2.1. After enabling gzip, I get randomly FormatException: Invalid ETag name exceptions. So it seems a suiteable workaround for me to let .NET Core do this job.

Upvotes: 13

baltzar
baltzar

Reputation: 476

Solved it by putting

app.UseResponseCompression();

before

app.UseMvc();

in Startup.Configure, i.e:

    public void Configure(IApplicationBuilder app, IHostingEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }
        else
        {
            app.UseHsts();
        }

        app.UseResponseCompression(); // <--
        app.UseHttpsRedirection();
        app.UseMvc(); // <--
    }

Upvotes: 5

Mohammad Dayyan
Mohammad Dayyan

Reputation: 22458

To Enable GZIP in .net core 2.*
1. Install Microsoft.AspNetCore.ResponseCompression with Install-Package Microsoft.AspNetCore.ResponseCompression command or nuget package manager.
2. Add the following code into Startup.cs

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{

  app.UseResponseCompression();
  app.UseMvc();

}

public void ConfigureServices(IServiceCollection services)
{

  // Configure Compression level
  services.Configure<GzipCompressionProviderOptions>(options => options.Level = CompressionLevel.Fastest);

  // Add Response compression services
  services.AddResponseCompression(options =>
  {
      options.Providers.Add<GzipCompressionProvider>();
      options.EnableForHttps = true;
  });

}

Upvotes: 45

ashwathi
ashwathi

Reputation: 111

Got this issue resolved by adding response compression option property "EnableForHttps" as shown below:

services.AddResponseCompression(opt =>
        {
            opt.Providers.Add<GzipCompressionProvider>();
            opt.EnableForHttps = true;
        });
 services.Configure<GzipCompressionProviderOptions>(options => options.Level = 
 CompressionLevel.Fastest);

Upvotes: 11

greentrees
greentrees

Reputation: 63

I managed to enable the Response Compression Middleware when using IIS Express by removing 

<httpCompression ...> 
...
</httpCompression>

in .vs\config\applicationhost.config

Upvotes: 2

Alexander
Alexander

Reputation: 1

By placing the UseResponseCompression twice under each other I managed to make it work. I have no idea how this made it work. I am still looking for an accepted solution.

Upvotes: 0

Related Questions