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 explores subtle and undocumented difference regarding response compression and response buffering in ASP.NET Core depending on target framework.
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.