For the request itself, yes. mod_proxy_http2 follows the same pattern as mod_proxy_http. It does not setup a faked request_rec that mod_proxy_http does since I did not need it and did not see the point. Might have missed something.
> Am 09.02.2016 um 15:51 schrieb Yann Ylavic <ylavic....@gmail.com>: > > On Mon, Feb 8, 2016 at 6:07 PM, Stefan Eissing > <stefan.eiss...@greenbytes.de> wrote: >> FYI: I just checked in a very experimental mod_proxy_http2 that registers on >> h2:// and h2c:// proxy URLs. I did this naming to have the module totally >> separate from mod_proxy_http, not wanting to make a mess. > > Does mod_proxy_http2 (like mod_http2) still generates an HTTP/1 > request run through the "usual" hooks? > Can a module/hook/filter (eg. rewrite, headers, security, ...) still > see/modify/refuse the inner HTTP/1?
