Strona głównaUżytkownik

tpeczek | użytkownik

1 655,61
7 dni, 2 godziny, 12 minut temu
6 grudnia, 2016

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.

Dziel się z innymi:
[EN] Server-Sent Events (or WebSockets) broadcasting in load balancing scenario with Redis

Web 1123 dni, 10 godzin, 30 minut temu tpeczek 48 źrodło rozwiń

This post shows how SSL Acceleration (Offloading) scenario can be supported in ASP.NET Core.

Tagi: Asp.Net Core, ssl
Dziel się z innymi:
[EN] Supporting SSL Acceleration (Offloading) in ASP.NET Core

Web 1135 dni, 11 godzin, 27 minut temu tpeczek 38 źrodło rozwiń

This post explores various approaches to concurrent requests limit.

Tagi: Asp.Net Core
Dziel się z innymi:
[EN] Implementing concurrent requests limit in ASP.NET Core for fun and education

Web 1158 dni, 10 godzin, 1 minutę temu tpeczek 61 źrodło rozwiń

This post explores subtle and undocumented difference regarding response compression and response buffering in ASP.NET Core depending on target framework.

[EN] ASP.NET Core, response compression, response buffering and subtle difference between .NET Framework and .NET Core

Web 1170 dni, 13 godzin, 2 minuty temu tpeczek 84 źrodło rozwiń

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.

Dziel się z innymi:
[EN] WebSocket per-message compression in ASP.NET Core

Web 1185 dni, 20 godzin, 32 minuty temu tpeczek 70 źrodło rozwiń

This post focuses on Cross-Site WebSocket Hijacking vulnerability and how to protect against it.

Dziel się z innymi:
[EN] Preventing Cross-Site WebSocket Hijacking in ASP.NET Core

Web 1198 dni, 19 godzin, 36 minut temu tpeczek 53 źrodło rozwiń

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.

[EN] WebSocket subprotocol negotiation in ASP.NET Core

Web 1214 dni, 20 godzin, 40 minut temu tpeczek 79 źrodło rozwiń

There is a number of Web APIs which allow measuring performance of web applications. The youngest member of that family is Server Timing API which allows communicating the server performance metrics to the client. This article shows how this API can be used in ASP.NET Core.

Dziel się z innymi:
[EN] Feeding Server Timing API from ASP.NET Core

Web 1228 dni, 17 godzin, 57 minut temu tpeczek 52 źrodło rozwiń

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.

Dziel się z innymi:
[EN] Generating documentation with DocFX as part of VS solution

Inne 1249 dni, 23 godziny, 40 minut temu tpeczek 36 źrodło rozwiń

Google's Certificate Transparency project is an open framework for monitoring and auditing SSL certificates. Starting April 2018 Chrome will require compliance with Certificate Transparency. Expect-CT Extension for HTTP will introduce a way to test the Certificate Transparency policy and this article shows how it can be used once it arrives.

Dziel się z innymi:
[EN] Preparing for Chrome's Certificate Transparency policy - Expect-CT with reporting in ASP.​NET Core

Web 1266 dni, 9 godzin, 7 minut temu tpeczek 29 źrodło rozwiń

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?

Dziel się z innymi:
[EN] Reconfiguring CORS policy in ASP.NET Core at runtime

Web środa, 26 kwietnia 2017 07:24:37 GMT tpeczek 25 spam? źrodło rozwiń

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.

Dziel się z innymi:
[EN] HTTP/2 with Server Push proof of concept for ASP.NET Core HttpSysServer

Web 1299 dni, 8 godzin, 44 minuty temu tpeczek 50 źrodło rozwiń

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.

[EN] Extending ASP.NET Core response compression with support for Brotli

Web 1316 dni, 21 godzin, 9 minut temu tpeczek 20 źrodło rozwiń

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.

Dziel się z innymi:
[EN] Supporting Encrypted Content-Encoding in HttpClient (Part 2 of 2) - Decoding

Web wtorek, 7 marca 2017 21:58:27 GMT tpeczek 8 spam? źrodło rozwiń

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.

Dziel się z innymi:
[EN] Supporting Encrypted Content-Encoding in HttpClient (Part 1 of 2) - Encoding

Web 1335 dni, 22 godziny, 15 minut temu tpeczek 41 źrodło rozwiń

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.

[EN] Server-Sent Events (SSE) support for ASP.NET Core

Web 1350 dni, 22 godziny, 50 minut temu tpeczek 189 źrodło rozwiń

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.

Dziel się z innymi:
[EN] Entity Framework - new() vs DbSet.Create()

Inne 1358 dni, 20 godzin, 5 minut temu tpeczek 205 źrodło rozwiń

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.

Dziel się z innymi:
[EN] HTTP/2 Server Push and ASP.NET MVC - Cache Digest

Web 1382 dni, 22 godziny, 47 minut temu tpeczek 95 źrodło rozwiń

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.

Dziel się z innymi:
[EN] Entity Framework 6 - Dynamically creating temporary tables from IQueryable (Part 2 of 2)

Inne 1390 dni, 5 godzin, 20 minut temu tpeczek 201 źrodło rozwiń

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.

Dziel się z innymi:
[EN] HTTP/2 Server Push and ASP.NET MVC

Web 1404 dni, 4 godziny, 12 minut temu tpeczek 124 źrodło rozwiń

1 2 3 4


(32 895,6)
(32 816,53)
(27 178,29)
(21 178,88)
(20 336,33)
(13 018,14)
(10 516,6)
(9 775,28)
(8 478,28)
(6 837,96)
(6 214,22)
(5 393,84)
(4 157,41)
(4 026,73)
(3 908,07)
(3 599,64)
(3 448,35)
(3 318,39)
(3 224,66)
(3 206,43)