httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yann Ylavic <>
Subject mod_proxy_http2 questions (was: [VOTE] backport mod_proxy_http2 to 2.4.x as experimental)
Date Thu, 10 Mar 2016 15:48:47 GMT
Hi Stefan,

sorry I didn't look closely enough in mod_proxy_http2's code yet to
answer the following questions by myself, so I'm asking here...

On Wed, Mar 9, 2016 at 1:53 PM, Stefan Eissing
<> wrote:
> When called inside a HTTP/1.1 connection, it will open/reuse
> an existing HTTP/2 backend connection for this one request.
> When called inside a HTTP/2 connection, new requests can be
> transferred to an already ongoing backend HTTP/2 connection
> for the same master.

I can follow the request path which traverses the "normal" http/1
hooks/filters (after the http/2 ones in the latter case), but the
response seems to be handled solely in the http2 code.

Am I right to think that any registered request or connection output
filter will get called as usual with an HTTP/1 response?

It may not make much sense for things like mod_deflate (already
integrated in h2) but others like mod_headers/security/third-party
working at the request level would still want to play here...

Also, what about filters registered on the backend connection?
With mod_proxy_http the proxy_create_req hook allows this and for
example I (will) use it in a patch (about to be proposed) to
mod_logio/mod_status for per-vhost counters (rated incoming and
outgoing connections, requests, bytes, TTFB, TTLB, ..., on both the
client and backend sides, implemented with some (new) mod_logio
connection filters).
Since there is no "fake" request_rec used/needed in mod_proxy_http2,
the is no such hook, but I guess there can be one (or even several
more specific to h2, dunno)...
Anyway, that is surely not a primary goal, I'm just thinking out loud here :)


View raw message