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?
tpeczek | użytkownik
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.
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.
In previous post I've shown how HttpClient can be extended with payload encryption capabilities by providing support for aes128gcm encoding. In this post I'm going to extend Aes128GcmEncoding class with decoding capabilities.
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.
The web socket protocol is currently the most popular one for pushing data to browsers, however it's not the only one. The Server-Sent Events (SSE) is a very interesting alternative which can provide better performance for specific use cases. In this post I'm going to show it can be used with ASP.NET Core.
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.
In previous post I've shown how a temporary table can be generated based on IQueryable and then reused in subsequent queries. I have also pointed out a serious limitation. The goal of this post is to address that limitation and touch on unit testing aspect.
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.
Some time ago I've written about HtmlHelper providing support for Content Security Policy. The solution presented worked well, but it required quite nasty markup. With ASP.NET Core MVC there is a new tool for this kind of tasks - TagHelpers.
I'm a huge fan of entity based and result set based relational mapping (classic ORMs). I'm also huge fan of DML based relational mapping (micro ORMs). In general I'm a huge fan of every technology that allows me to get the job done in the best possible way. I believe that one should never limit himself to single approach within a project - it should always be about choosing the best tool for the job. But sometimes there are real life constraints (licensing, business, politics etc.) which are limiting the...
macko (32 816,53)
http://pawlos.blo... (31 603,45)
pzielinski (27 178,29)
gordon_shumway (21 178,87)
paduda (20 336,33)
psz750 (13 018,14)
rroszczyk (10 383,88)
Damian (9 041,08)
danielplawgo (7 235,99)
arek (6 807,94)
burczu (6 214,22)
PaSkol (5 393,84)
lukaszgasior (4 097,38)
jj09 (3 578,06)
jedmac (3 318,39)
http://jakub-flor... (3 224,66)
CaMeL (2 954,87)
spetz (2 798,25)
mnikolajuk (2 596,93)
lkurzyniec (2 590,69)