Recently I've been playing a lot with HTTP/2 and with ASP.NET Core but I didn't had chance to play with both at once. I've decided it's time to change that. Unfortunately the direct HTTP/2 support for Kestrel is still in backlog. Luckily Kestrel is not the only HTTP server implementation for ASP.NET Core.
This is a follow up to my previous post on HTTP/2 Server Push which deep dives into subject of client side caching and explores the Cache Digest proposal.
One of the new features in HTTP/2 is Server Push. It allows the server to send resources to the browser without having to wait for the browser to request it. I don't intend to provide comprehensive information regarding HTTP/2 Server Push here as there is a lot of resources on the web doing that already, all I want is to play a little with Server Push in context of ASP.NET MVC.