Enable dynamic routing

[ycrumeyrolle]

The proxy should be able to send the underlying request to different hosts based on the request context.

For example
Incoming request: https://mysite.com/api1/
Outgoing request : http://myapi1.local/

Incoming request: https://mysite.com/api2/
Outgoing request : http://myapi2.local/

We could imagine a IProxyRouter. Default implementation is a DirectProxyRouter (the current implementation). Other implementation could be a rule-based router.
This will allow to have a basic reverse proxy.

[Tratcher]

It makes sense to enable forwarding to multiple back-ends. The first scenario I'd test would be for load balancing, but you could have other rules as well.

At the lowest level it could be as simple as a Func on the Options that takes an HttpContext and returns a destination url.

[mkosieradzki]

It seems I have created a duplicate issue #43 - sorry for that - I will close it. However I would like to grab this one.

[kevinrood]

I would like to see dynamic routing added as well.

[mkosieradzki]

@kevinrood
It's already done #46 it's waiting for merge.

[kevinrood]

@mkosieradzki great to hear. What is the performance like so far?

[mkosieradzki]

@kevinrood Should be great as the proxy layer is really thin, fully asynchronous and it's really bound to the HttpSys/Kestrel + HttpClient performance. But have not done any performance tests yet.

[aspnet-hello]

This issue was moved to aspnet/Home#2503