Yeah, the more I think about it,  ap_get_remote_host() is
currently broken wrt how it handles useragent_ip and client_ip.

Will likely try to patch this on trunk sometime today...

On Sep 11, 2014, at 9:35 AM, Martynas Bendorius <marty...@martynas.it> wrote:

> Yes, we may re-phrase it like that, if we'd like to fix it in apache source 
> (and not documentation) :) Currently ap_get_remote_host in server/core.c 
> doesn't return useragent_ip, and instead of it we get conn->client_ip.
> 
> Best regards,
> Martynas Bendorius
> 
> On 9/11/14 4:21 PM, Jim Jagielski wrote:
>> isn't the question rather "What should ap_get_remote_host()
>> return?"?
>> 
>> On Sep 11, 2014, at 8:17 AM, Martynas Bendorius <marty...@martynas.it> wrote:
>> 
>>> Hello,
>>> 
>>> Would it be possible to change the documentation of mod_remoteip for 2.4 
>>> (http://httpd.apache.org/docs/2.4/mod/mod_remoteip.html), and get "is 
>>> reported by mod_status" removed from the page? As it leds Apache customers 
>>> to believe that it will report a real (useragent) IP instead of a proxy one 
>>> in server-status page. useragent_ip is not even available in scoreboard, 
>>> which is used by mod_status, so it's not available for mod_status.
>>> 
>>> This has been already discussed here: 
>>> https://issues.apache.org/bugzilla/show_bug.cgi?id=55886
>>> 
>>> Thank you!
>>> 
>>> Best regards,
>>> Martynas Bendorius
>>> 
>> 
> 

Reply via email to