Strona głównaUżytkownik

tpeczek | użytkownik

12 godzin, 45 minut temu
6 grudnia, 2016

This post explores how the HEAD method is handled by ASP.NET Core and proposes solutions to some problems.

Dziel się z innymi:
[EN] Exploring HEAD method behavior in ASP.NET Core

Web 3 dni, 13 godzin, 37 minut temu tpeczek 68 rozwiń

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 18 dni, 14 godzin, 49 minut temu tpeczek 39 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 30 dni, 15 godzin, 47 minut temu tpeczek 37 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 53 dni, 14 godzin, 21 minut temu tpeczek 58 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 65 dni, 17 godzin, 21 minut temu tpeczek 83 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 81 dni, 51 minut temu tpeczek 66 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 93 dni, 23 godziny, 56 minut temu tpeczek 51 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 110 dni, 59 minut temu tpeczek 70 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 123 dni, 22 godziny, 17 minut temu tpeczek 49 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 145 dni, 3 godziny, 59 minut temu tpeczek 35 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 161 dni, 13 godzin, 26 minut temu tpeczek 19 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 26 kwietnia 2017 07:24:37 GMT tpeczek 22 spam? 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 194 dni, 13 godzin, 3 minuty temu tpeczek 42 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 212 dni, 1 godzinę, 29 minut temu tpeczek 17 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 7 marca 2017 21:58:27 GMT tpeczek 8 spam? 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 231 dni, 2 godziny, 34 minuty temu tpeczek 40 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 246 dni, 3 godziny, 9 minut temu tpeczek 132 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 254 dni, 25 minut temu tpeczek 203 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 278 dni, 3 godziny, 7 minut temu tpeczek 84 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 285 dni, 9 godzin, 39 minut temu tpeczek 141 rozwiń

1 2
Szkolenia SecurITum


Dodaj nowe Zobacz wszystkie



macko (32 816,53)


http://pawlos.blo... (32 078,52)


pzielinski (27 178,29)


gordon_shumway (21 178,87)


paduda (20 336,33)


psz750 (13 018,14)


rroszczyk (10 386,57)


Damian (9 173,12)


danielplawgo (7 235,99)


arek (6 807,95)


burczu (6 214,22)


PaSkol (5 393,84)


lukaszgasior (4 097,38)


jj09 (3 733,06)


spetz (3 363,34)


jedmac (3 318,39)


http://jakub-flor... (3 224,66)


CaMeL (2 954,87)


dpawlukiewicz (2 811,22)


lkurzyniec (2 737,06)