I won't be able to do this today, but can tomorrow. Otherwise anyone with time to merge back the change, please do.
> Am 13.06.2016 um 20:59 schrieb Gregg Smith <g...@gknw.net>: > > I have the to connect this module in the traditional windows build but as of > right now it's using h2_util.c which Bill had an objection to. See his > comments http://marc.info/?l=apache-httpd-dev&m=146543811201820&w=2 > > So to me that seems to be a -1 to mod_proxy_http2, at minimum on Windows. In > trunk Stefan seems to have chosen option 3 in Bill's list and that is > h2_proxy_util.c. > > If I knew that was going to be backported I would add the rest of the bits > needed to use h2_proxy_util.c. If it is not going to make it, then I will not > commit anything and there will be no mod_proxy_http2 in 2.4.21 on Windows. If > this gets in overnight and you tag in the morning, I may not be out of bed > yet due to the time difference. > > That's where my concern is. Make sense? > > >> On 6/13/2016 11:43 AM, Jim Jagielski wrote: >> What needs to be done? >> >>> On Jun 13, 2016, at 2:20 PM, Gregg Smith<g...@gknw.net> wrote: >>> >>> Hi Stefan, >>> >>> Any plans to backport this before Jim tags 2.4.21 tomorrow? >>> >>> Thanks, >>> >>> Gregg >
