[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):

 What is this being used for (other than logging)?

 If it's important to know the end user's IP address, then maybe it's
 worthwhile determining whether they're behind a proxy and recording the
 HTTP_CLIENT_IP or X_FORWARDED_FOR values.

 These can be problematic though; sometimes not containing a single IP,
 sometimes with junk embedded.  And they come from the client, so can't be
 trusted the same way as REMOTE_ADDR.

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