Cool. On Sep 12, 2014, at 8:57 AM, Martynas Bendorius <[email protected]> wrote:
> Super! I've tested it and it solves all the problems with mod_status. Thank > you. > > Best regards, > Martynas Bendorius > > On 9/12/14 3:46 PM, Jim Jagielski wrote: >> Fixed in: >> >> http://svn.apache.org/r1624349 >> >> On Sep 11, 2014, at 12:23 PM, Jim Jagielski <[email protected]> wrote: >> >>> Well, fixing this *specifically* for mod_status is >>> easy, but, as you say, the problem is more systemic >>> than that. >>> >>> On Sep 11, 2014, at 12:13 PM, [email protected] wrote: >>> >>>> --------- Original Message --------- >>>> Subject: Re: mod_status: Apache 2.4 incorrect IP (proxy, not useragent_ip) >>>> on server-status page >>>> From: "Jim Jagielski" <[email protected]> >>>> Date: 9/11/14 10:45 am >>>> To: [email protected] >>>> >>>> Ugg. Yeah; we should actually have a complimentary version >>>> that takes request_req as the param, not conn_rec. >>>> >>>> ap_get_remote_host_r()?? >>>> >>>> Considered that. But that still breaks mod_remoteip's advertised >>>> behavior against third party modules until they adapt. So I'd written >>>> this off as a non-starter :( >>>> >>>> Ugly. >>>> >>>> Indeed >>> >> >
