application-defined handlers don't make sense

[marten-seemann]

The URL should is already encoded in the URI template. Unfortunately, it doesn't seem like the URI template library allows us to extract it though, so we might need to jump through some hoops to obtain it.

[marten-seemann]

On the other hand, we want to give the application a lot of control of the processing of the HTTP request: it should be possible to use HTTP headers, for example for (basic / unprompted / bespoke) authentication.

Maybe we just need to document that it doesn't make sense to configure an URI template with path1, and add it on an HTTP handler for path2?

[marten-seemann]

For inspiration, we should take a look at popular Go proxying libraries like goproxy.