On Wed, 23 Nov 2011 11:56:25 -0600 "William A. Rowe Jr." <[email protected]> wrote:
> +1 to this rename, it's much more sensible than "effective", "phys", > "" et al, but reverse them. > > client_ip / client_addr is the immediate client of httpd, which may > be a load balancer or transparent proxy or normal proxy if mod_remoteip > has been introduced. Not really. The HTTP client is the end-of-line. The intermediary is an HTTP proxy, not a client. > remote_ip / remote_addr is the recognized _authenticated_ address. Indeed, that's terminology that goes right back to apache prehistory. > This has the additional advantage of *breaking* existing c->remote_ip > references and forcing the module author to choose which they mean for > their purposes (most would refer to the authenticated address). An interesting take on it! But use of remote_ip and remote_addr goes further than that. Changing their semantics in CGI (and its imitators from PHP to mod_rewrite) would *silently* break apps, so a firm -1 to that. And divorcing conn->remote_ip from the CGI/etc gets fearsomely confusing! -- Nick Kew
