Overriding externally set headers and HTTP status codes in ASP.NET Core

Tue, 10 Jul 2018 11:34:00 +0000

I was working on an interesting issue in an ASP.NET Core recently. An external framework was responsible for creating an HTTP Response, and I was only in control of a little component that customized some internal behaviours (via a relevant extensibility point), without being able to influence the final response sent over HTTP.

This is common if you think about extending things like CMS systems or specialized services like for example Identity Server. In those situations, more often than not, the framework would be highly opinionated in what it is trying to do at the HTTP boundaries and as a result, trying to override the HTTP status codes or headers it produces may not be easy.

Let’s have a look at a simple generic workaround.

Self-issuing an IdentityServer4 token in an IdentityServer4 service

Tue, 10 Oct 2017 15:00:29 +0000

When building logic around the IdentityServer4 extensibility points, it is sometimes necessary to dynamically issue a token, with which your code can then call some external endpoints or dependencies.

Turns out that rather than round-tripping back to same IdentityServer4 instance over the network to get that token, there is a more efficient and quicker way to do it. Let’s have a look.

Identity Server on Strathweb. A free flowing tech monologue.

Overriding externally set headers and HTTP status codes in ASP.NET Core

Self-issuing an IdentityServer4 token in an IdentityServer4 service