Q: Questions - name, performance?

[Peperud]

1. Name - wouldn't ReverseProxy be a better fitting name?
2. Performance - what should be expected, compared to say nginx, or perhaps a closer match - golang's httputil.ReverseProxy?
3. Limitations?

[Chris Ross]

1. Yes.
2. So far this is just a proof of concept, no significant perf work has been done.
3. The configuration isn't very flexible. No load balancing. No HTTP/2 support. No WebSocket support. etc..

[Peperud]

A suggestion - in addition to dynamic routing it will be useful if there is a way to dynamically filter (add/remove/change) headers. In both directions.
Perhaps having the middleware take a resolver (instead of straight options), with method(s) for resolving whatever it needs at runtime (destination, header filters etc.). And a default resolver implementation that handles the static options configuration...