[mapguide-trac] #539: Implement CLIENTIP and CLIENTAGENT tracking in the Server's Access.log

[MapGuide Open Source]

#539: Implement CLIENTIP and CLIENTAGENT tracking in the Server's Access.log
----------------------+-----------------------------------------------------
 Reporter:  tonyfang  |         Owner:  tonyfang
     Type:  defect    |        Status:  closed  
 Priority:  medium    |     Milestone:  2.1     
Component:  Web API   |       Version:  2.0.0   
 Severity:  minor     |    Resolution:  fixed   
 Keywords:            |   External_id:          
----------------------+-----------------------------------------------------
Comment (by jbirch):

 Yes, if you have to choose one, REMOTE_ADDR is best.

 On one of my hobby sites, I see a large number of requests coming from
 transparent proxies such as Shaw Cable's.  The users behind these proxies
 have publicly reachable IP addresses, but their web requests are being
 stuffed through a caching proxy.  I've found it valuable to have
 X_FORWARDED_FOR when tracking down abusive users.

 Not a big deal, just thought I'd comment.

-- 
Ticket URL: <https://trac.osgeo.org/mapguide/ticket/539#comment:5>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals