Add response compression in .NET Core

- 
services.AddResponseCompression(options => options.Providers.Add<GzipCompressionProvider>());

app.UseResponseCompression();

Comments

Post a Comment

Popular posts from this blog

C# Record Serialization

-
Image
With .NET 5, you get a new concept called record . Lots of cool things, one of which is that you can serialize and deserialize with JSON just like a class, except you don't need to define properties one at a time, or even the body of the type. Apparently XML serialization doesn't quite work, so stick with JSON. View code on GitHub
Read more

Razor Pages AJAX

-
Image
Razor Pages is a fantastic alternative to ASP.NET MVC. Here's one reason - CSRF protection is included by default. That's great news, but it means that you can't execute AJAX posts as easily. Fortunately, it's still not difficult to do a post. Here's how. View code on GitHub
Read more

Versioned content in MVC

-
When you add a script or stylesheet to your HTML page, those requests can be cached by the browser, potentially providing outdated content to the browser. If you’re not using a bundler or anything fancy like that, then the only way to prevent this problem is to create a brand new URL whenever your script file or stylesheet changes. This is easily accomplished with a querystring, so if your app was previously using app.js?v=1 and you change that to app.js?v=2, the browser will definitely not use the cached version, and will instead make a new request to the server, and pull the latest one. Using the following technique, you can guarantee that you’ll always pull the latest script and stylesheet when working in dev, and when in production, you can define a “version key”, possibly in a config file or database, and if you ever update just the static content, you would only need to update that key, and it would force all browsers to pull new content. public static class HtmlExtensions {...
Read more