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

 Just for logging.
 As it says in the Description, the Map Admin was already sending these
 parameters to the server and getting them logged in the Access.log.

 The submissions associated with this ticket complete the work for the rest
 of the applications (Ajax, Web Tier test pages, Schema Report). And also
 implements the REMOTE_ADDR IP checking in the Apache/ISAPI/CGI agents for
 HTTP requests.

 I figured REMOTE_ADDR is the most useful IP information for the
 Access.log. If the user is behind a proxy, the IP behind the proxy may not
 be very meaningful to the Access.log.

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