Thanks to your feedback, I just realized there’s a typo that makes this not make any sense. It should read:
Additionally, upstream addresses cannot contain paths or query strings, as that would imply simultaneous rewriting the request while proxying, which behavior is not defined or supported.
Okay, well, I think that would be a little ridiculous for any reverse proxy, but just to be extra clear how about we change it to:
Additionally, upstream addresses specified in configuration cannot contain paths or query strings, as that would imply simultaneous rewriting the request while proxying, which behavior is not defined or supported.
(But to be honest, I do think that it’s pretty obvious that we’re already talking about upstream addresses defined in configuration, since that’s literally what the whole section is about.)
To be clear, the handle directive has nothing to do with proxying. The reverse proxy will always (by default) pass through pretty much every aspect of the request except the few things that are noted (a few hop-by-hop proxy headers, for example). The request URI components, all other headers, and the body go through unchanged.
Yep! Our wiki category lets anyone share their expertise and discuss improvements to their articles. It doesn’t require any pull requests or code review, and anyone can easily edit and improve on contributions.