When IIS is used as reverse proxy for ASP.NET Core application it can alter the response. This post shows how to prevent one of such alterations - response compression.

This post shows how Redis can be used to solve the problem of SSE or WebSockets broadcasting for ASP.NET Core applications behind load balancer.

This post explores various approaches to concurrent requests limit.

A number of browsers support WebSocket per-message compression out of the box. This post shows how it can be used in ASP.NET Core.

WebSocket is the closest API to a network socket available in browser. This makes it probably the most flexible transport which a web application can use. That flexibility comes at price. From WebSocket perspective the message content is opaque. This means that client and server must agree on application subprotocol. WebSocket provides a simple subprotocol negotiation mechanism which helps in that task.

On of the hardest parts of getting an open source project into state which allows others to use it effectively is creating documentation. This post shows how you can generate documentation directly from source code by using DocFx.

ASP.NET Core comes with ready to use Cross Origin Resource Sharing support. The usage is very straightforward and nicely described in documentation, but what if there is a need to reconfigure the policy at runtime?

The amount of transferred data matters. On one hand it often contributes to the cost of running a service and on the other a lot of clients doesn't have as fast connections as we would like to believe. This is why response compression is one of key performance mechanisms in web world.

The "Encrypted Content-Encoding for HTTP" aims at providing standard solution for encrypting the contents of a HTTP message so that when the payload is stored, only someone with the appropriate key can read it. In this and next post I'm going to show how it can be used with HttpClient.

This is one of those "I had to explain this couple times already so next time I want something I can redirect people to" kind of post. What I want to write about is difference in behavior between using new() and DbSet.Create() for instantiating new entities.