/ProxyKit

A toolkit to create code-first HTTP reverse proxies on ASP.NET Core

Primary LanguageC#Apache License 2.0Apache-2.0

Image

ProxyKit Build Status NuGet

A toolkit to create code-first HTTP Reverse Proxies hosted in ASP.NET Core as middleware. This allows focused code-first proxies that can be embedded in existing ASP.NET Core applications or deployed as a standalone server. Deployable anywhere ASP.NET Core is deployable such as Windows, Linux, Containers and Serverless (with caveats).

Having built proxies many times before, I felt it is time to make a package. Forked from ASP.NET labs, it has been heavily modified with a different API, to facilitate a wider variety of proxying scenarios (i.e. routing based on a JWT claim) and interception of the proxy requests / responses for customization of headers and (optionally) request / response bodies. It also uses HttpClientFactory internally that will mitigate against DNS caching issues making it suitable for microservice / container environments.

1. Quick Start

1.1. Install

ProxyKit is a NetStandard2.0 package. Install into your ASP.NET Core project:

dotnet add package ProxyKit

1.2. Forward HTTP Requests

In your Startup, add the proxy service:

public void ConfigureServices(IServiceCollection services)
{
    ...
    services.AddProxy();
    ...
}

Forward HTTP requests to upstream-server:5001:

public void Configure(IApplicationBuilder app)
{
    app.RunProxy(context => context
        .ForwardTo("http://upstream-server:5001/")
        .AddXForwardedHeaders()
        .Send());
}

What is happening here?

  1. context.ForwardTo(upstreamHost) is an extension method on HttpContext that creates and initializes an HttpRequestMessage with the original request headers copied over, yielding a ForwardContext.
  2. AddXForwardedHeaders adds X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-PathBase headers to the upstream request.
  3. Send Sends the forward request to the upstream server and returns an HttpResponseMessage.
  4. The proxy middleware then takes the response and applies it to HttpContext.Response.

Note: RunProxy is terminal - anything added to the pipeline after RunProxy will never be executed.

1.3. Forward WebSocket Requests

Forward WebSocket requests to upstream-server:5002:

public void Configure(IApplicationBuilder app)
{
    app.UseWebSockets();
    app.UseWebSocketProxy(
        context => new Uri("ws://upstream-host:80/"),
        options => options.AddXForwardedHeaders());
}

What is happening here?

  1. app.UseWebSockets() must first be added otherwise websocket requests will never be handled by ProxyKit.
  2. The first parameter must return the URI of the upstream host with a scheme of ws://.
  3. The second parameter options allows you to do some customisation of the initial upstream requests such as adding some headers.

2. Core Features

2.1. Customising the upstream HTTP request

One can modify the upstream request headers prior to sending them to suit customisation needs. ProxyKit doesn't add, remove, nor modify any headers by default; one must opt in any behaviours explicitly.

In this example we will add a X-Correlation-ID header if the incoming request does not bear one:

public const string XCorrelationId = "X-Correlation-ID";

public void Configure(IApplicationBuilder app)
{
    app.RunProxy(context =>
    {
        var forwardContext = context.ForwardTo("http://upstream-server:5001/");
        if (!forwardContext.UpstreamRequest.Headers.Contains(XCorrelationId))
        {
            forwardContext.UpstreamRequest.Headers.Add(XCorrelationId, Guid.NewGuid().ToString());
        }
        return forwardContext.Send();
    });
}

This can be encapsulated as an extension method:

public static class CorrelationIdExtensions
{
    public const string XCorrelationId = "X-Correlation-ID";
    
    public static ForwardContext ApplyCorrelationId(this ForwardContext forwardContext)
    {
        if (!forwardContext.UpstreamRequest.Headers.Contains(XCorrelationId))
        {
            forwardContext.UpstreamRequest.Headers.Add(XCorrelationId, Guid.NewGuid().ToString());
        }
        return forwardContext;
    }
}

... making the proxy code a little nicer to read:

public void Configure(IApplicationBuilder app)
{
    app.RunProxy(context => context
        .ForwardTo("http://upstream-server:5001/")
        .ApplyCorrelationId()
        .Send());
}

2.2. Customising the upstream response

The response from an upstream server can be modified before it is sent to the client. In this example we are removing a header:

public void Configure(IApplicationBuilder app)
{
    app.RunProxy(async context =>
    {
        var response = await context
            .ForwardTo("http://localhost:5001/")
            .Send();

        response.Headers.Remove("MachineID");

        return response;
    });
}

2.3. X-Forwarded Headers

2.3.1. Client Sent X-Forwarded-Headers

⚠️ To mitigate against spoofing attacks and misconfiguration ProxyKit does not copy X-Forward-* headers from the incoming request to the upstream request by default. Copying them requires opting in; see 2.3.3 Copying X-Forwarded headers below.

2.3.2. Adding X-Forwarded-* Headers

Many applications will need to know what their "outside" host / URL is in order to generate correct values. This is achieved using X-Forwarded-* and Forwarded headers. ProxyKit supports applying X-Forward-* headers out of the box (applying Forwarded headers support is on backlog). At the time of writing, Forwarded is not supported in ASP.NET Core.

To add X-Forwarded-* headers to the request to the upstream server:

public void Configure(IApplicationBuilder app)
{
    app.RunProxy(context => context
        .ForwardTo("http://upstream-server:5001/")
        .AddXForwardedHeaders()
        .Send());
}

This will add X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Proto headers to the upstream request using values from HttpContext. If the proxy middleware is hosted on a path and a PathBase exists on the request, then an X-Forwarded-PathBase is also added.

2.3.3. Copying X-Forwarded headers

Chaining proxies is a common pattern in more complex setups. In this case, if the proxy is an "internal" proxy, you will want to copy the "X-Forwarded-*" headers from previous proxy. To do so, use CopyXForwardedHeaders():

public void Configure(IApplicationBuilder app)
{
    app.RunProxy(context => context
        .ForwardTo("http://upstream-server:5001/")
        .CopyXForwardedHeaders()
        .Send());
}

You may optionally also add the "internal" proxy details to the X-Forwarded-* header values by combining CopyXForwardedHeaders() and AddXForwardedHeaders() (note the order is important):

public void Configure(IApplicationBuilder app)
{
    app.RunProxy(context => context
        .ForwardTo("http://upstream-server:5001/")
        .CopyXForwardedHeaders()
        .AddXForwardedHeaders()
        .Send());
}

2.4. Configuring ProxyKit's HttpClient

When adding the Proxy to your application's service collection, there is an opportunity to configure the internal HttpClient. As HttpClientFactory is used, its builder is exposed for you to configure:

services.AddProxy(httpClientBuilder => /* configure http client builder */);

Below are two examples of what you might want to do:

  1. Configure the HTTP Client's timeout to 5 seconds:

    services.AddProxy(httpClientBuilder =>
    httpClientBuilder.ConfigureHttpClient =
        client => client.Timeout = TimeSpan.FromSeconds(5));

  2. Configure the primary HttpMessageHandler. This is typically used in testing to inject a test handler (see Testing below).

    services.AddProxy(httpClientBuilder =>
    httpClientBuilder.ConfigurePrimaryHttpMessageHandler = 
        () => _testMessageHandler);

2.5. Error handling

When HttpClient throws, the following logic applies:

  1. When upstream server is not reachable, then 503 ServiceUnavailable is returned.
  2. When upstream server is slow and client timeouts, then 504 GatewayTimeout is returned.

Not all exception scenarios and variations are caught, which may result in a InternalServerError being returned to your clients. Please create an issue if a scenario is missing.

2.6. Testing

As ProxyKit is a standard ASP.NET Core middleware, it can be tested using the standard in-memory TestServer mechanism.

Often you will want to test ProxyKit with your application and perhaps test the behaviour of your application when load balanced with two or more instances as indicated below.

                               +----------+
                               |"Outside" |
                               |HttpClient|
                               +-----+----+
                                     |
                                     |
                                     |
                         +-----------+---------+
    +-------------------->RoutingMessageHandler|
    |                    +-----------+---------+
    |                                |
    |                                |
    |           +--------------------+-------------------------+
    |           |                    |                         |
+---+-----------v----+      +--------v---------+     +---------v--------+
|Proxy TestServer    |      |Host1 TestServer  |     |Host2 TestServer  |
|with Routing Handler|      |HttpMessageHandler|     |HttpMessageHandler|
+--------------------+      +------------------+     +------------------+

RoutingMessageHandler is an HttpMessageHandler that will route requests to specific hosts based on the origin it is configured with. For ProxyKit to forward requests (in memory) to the upstream hosts, it needs to be configured to use the RoutingMessageHandler as its primary HttpMessageHandler.

Full example can been viewed in Recipe 6.

2.7. Load Balancing

Load balancing is a mechanism to decide which upstream server to forward the request to. Out of the box, ProxyKit currently supports one type of load balancing - Weighted Round Robin. Other types are planned.

2.7.1. Weighted Round Robin

Round Robin simply distributes requests as they arrive to the next host in a distribution list. With optional weighting, more requests are sent to the host with the greater weight.

public void Configure(IApplicationBuilder app)
{
    var roundRobin = new RoundRobin
    {
        new UpstreamHost("http://localhost:5001/", weight: 1),
        new UpstreamHost("http://localhost:5002/", weight: 2)
    };

    app.RunProxy(
        async context =>
        {
            var host = roundRobin.Next();

            return await context
                .ForwardTo(host)
                .Send();
        });
}

2.8. Typed Handlers

New in version 2.1.0

Instead of specifying a delegate, it is possible to use a typed handler. The reason you may want to do this is when you want to better leverage dependency injection.

Typed handlers must implement IProxyHandler that has a single method with same signature as HandleProxyRequest. In this example our typed handler has a dependency on an imaginary service to lookup hosts:

public class MyTypedHandler : IProxyHandler
{
    private IUpstreamHostLookup _upstreamHostLookup;

    public MyTypeHandler(IUpstreamHostLookup upstreamHostLookup)
    {
        _upstreamHostLookup = upstreamHostLookup;
    }

    public Task<HttpResponseMessage> HandleProxyRequest(HttpContext context)
    {
        var upstreamHost = _upstreamHostLookup.Find(context);
        return context
            .ForwardTo(upstreamHost)
            .AddXForwardedHeaders()
            .Send();
    }
}

We then need to register our typed handler service:

public void ConfigureServices(IServiceCollection services)
{
    ...
    services.AddSingleton<MyTypedHandler>();
    ...
}

When adding the proxy to the pipeline, use the generic form:

public void ConfigureServices(IServiceCollection services)
{
    ...
    appInner.RunProxy<MyTypedHandler>());
    ...
}

3. Recipes

Recipes are code samples that help you create proxy solutions for your needs. If you have any ideas for a recipe, or can spot any improvements to the ones below, please send a pull request! Recipes that stand test of time may be promoted to an out-of-the-box feature in a future version of ProxyKit.

3.1. Simple Forwarding

Forward request to a single upstream host.

src/Recipes/01_Simple.cs

3.2. Proxy Paths

Hosting multiple proxies on separate paths.

src/Recipes/02_Paths.cs

3.3. Claims Based Tenant Routing

Routing to a specific upstream host based on a TenantId claim for an authenticated user.

src/Recipes/03_TenantRouting.cs

3.4. Authentication offloading with Identity Server

Using IdentityServer to handle authentication before forwarding to upstream host.

src/Recipes/04_IdSrv.cs

3.5. Weighted Round Robin Load Balancing

Weighted Round Robin load balancing to two upstream hosts.

src/Recipes/05_RoundRobin.cs

3.6. In-memory Testing

Testing behaviour or your ASP.NET Core application by running two instances behind round robin proxy. Really useful if your application has eventually consistent aspects.

src/Recipes/06_Testing.cs

3.7. Customise Upstream Requests

Customise the upstream request by adding a header.

src/Recipes/07_CustomiseUpstreamRequest.cs

3.8. Customise Upstream Responses

Customise the upstream response by removing a header.

src/Recipes/08_CustomiseUpstreamResponse.cs

3.9. Consul Service Discovery

Service discovery for an upstream host using Consul.

src/Recipes/09_ConsulServiceDisco.cs

3.10. Copy X-Forwarded Headers

Copies X-Forwarded-For, X-Forwarded-Host, X-Forwarded-Proto and X-Forwarded-PathBase headers from the incoming request. Typically only done when the proxy is in a chain of known proxies. Is it NOT recommended that you blindly accept these headers from the public Internet.

src/Recipes/10_CopyXForwarded.cs

3.11. Caching Upstream Responses with CacheCow

Using CacheCow.Client to cache responses from upstream servers using standard HTTP caching headers.

src/Recipes/11_CachingWithCacheCow.cs

3.12. Conditional Proxying

Using app.UseWhen() to conditionally forward the request based on asserting a value on HttpContext.

src/Recipes/12_ConditionalProxying.cs

3.13. Client Certificate

Using a client certificate in requests to upstream hosts.

src/Recipes/13_ClientCertificate.cs

3.14. Source IP Blocking

Block requests from sources whose IP addresses is not allowed.

src/Recipes/14_SourceIPBlocking.cs

3.14. Source IP Blocking

Block requests from sources whose IP addresses is not allowed.

3.15. WebSockets

How to proxy WebSocket connections.

src/Recipes/14_WebSockets.cs

3.16. SignalR

Proxying for SignalR whose protocol requires both HTTP and WebSocket forwarding to upstream hosts.

src/Recipes/16_SignalR.cs

3.17. SignalR with Path

Proxying for SignalR on a specific path.

src/Recipes/17_SignalROnPath.cs

3.18. Automatic Decompression

Automatic decompression of responses from upstream hosts allowing response body manipulation.

src/Recipes/18_AutomaticDecompression.cs

4. Making upstream servers reverse proxy friendly

Applications that are deployed behind a reverse proxy typically need to be somewhat aware of that so they can generate correct URLs and paths when responding to a browser. That is, they look at X-Forward-* / Forwarded headers and use their values.

In ASP.NET Core, this means using the ForwardedHeaders middleware in your application. Please refer to the documentation for correct usage (and note the security advisory!).

Note: the Forwarded Headers middleware does not support X-Forwarded-PathBase. This means if you proxy http://example.com/foo/ to http://upstream-host/ the /foo/ part is lost and absolute URLs cannot be generated unless you configure your application's PathBase directly.

Related issues and discussions:

To support PathBase dynamically in your application with X-Forwarded-PathBase, examine the header early in your pipeline and set the PathBase accordingly:

var options = new ForwardedHeadersOptions
{
   ...
};
app.UseForwardedHeaders(options);
app.Use((context, next) => 
{
    if (context.Request.Headers.TryGetValue("X-Forwarded-PathBase", out var pathBases))
    {
        context.Request.PathBase = pathBases.First();
    }
    return next();
});

Alternatively you can use ProxyKit's UseXForwardedHeaders extension that performs the same as the above (including calling UseForwardedHeaders):

var options = new ForwardedHeadersOptions
{
   ...
};
app.UseXForwardedHeaders(options);

5. Performance considerations

According to TechEmpower's Web Framework Benchmarks, ASP.NET Core is up there with the fastest for plain text. As ProxyKit simply captures headers and async copies request and response body streams, it will be fast enough for most scenarios.

If absolute raw throughput is a concern for you, then consider nginx or alternatives. For me being able to create flexible proxies using C# is a reasonable tradeoff for the (small) performance cost. Note that what your specific proxy (and its specific configuration) does will impact performance so you should measure for yourself in your context.

On Windows, ProxyKit is ~3x faster than nginx. However, nginx has clearly documented that it has known performance issues on Windows. Since one wouldn't be running production nginx on Windows, this comparison is academic.

Memory wise, ProxyKit maintained a steady ~20MB of RAM after processing millions of requests for simple forwarding. Again, it depends on what your proxy does so you should analyse and measure yourself.

6. Note about serverless

Whilst it is possible to run full ASP.NET Core web application in AWS Lambda and Azure Functions it should be noted that Serverless systems are message based and not stream based. Incoming and outgoing HTTP request messages will be buffered and potentially encoded as Base64 if binary (so larger). This means ProxyKit should only be used for API (json) proxying in production on Serverless. (Though proxying other payloads is fine for dev / exploration / quick'n'dirty purposes.)

7. Comparison with Ocelot

Ocelot is an API Gateway that also runs on ASP.NET Core. A key difference between API Gateways and general Reverse Proxies is that the former tend to be message based whereas a reverse proxy is stream based. That is, an API Gateway will typically buffer every request and response message to be able to perform transformations. This is fine for an API Gateway but not suitable for a general reverse proxy performance wise nor for responses that are chunked-encoded. See Not Supported Ocelot docs.

Combining ProxyKit with Ocelot would give some nice options for a variety of scenarios.

8. How to build

Requirements: .NET Core SDK 2.2.100 or later.

On Windows:

.\build.cmd

On Linux:

./build.sh

9. Contributing / Feedback / Questions

Any ideas for features, bugs or questions, please create an issue. Pull requests gratefully accepted but please create an issue for discussion first.

I can be reached on twitter at @randompunter

10. Articles, blogs and other external links

logo is distribute by ChangHoon Baek from the Noun Project.