[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:  new     
   Priority:  medium    |   Milestone:  2.1     
  Component:  Web API   |     Version:  2.0.0   
   Severity:  minor     |    Keywords:          
External_id:            |  
------------------------+---------------------------------------------------
 The CLIENTIP and CLIENTAGENT parameters must be sent to the server in
 order for the Access.log to record them. Currently, only the Map Admin php
 application is doing so.

 The following changes are needed:

 * The Apache/ISAPI/CGI agent needs to figure out the IP address from the
 REMOTE_ADDR CGI Server variable and send it to the server. This takes care
 of the IP address for http server requests.

 * When a web application (like the Map Admin, Ajax Viewer, Fusion Viewer,
 Schema Report) creates an MgSiteConnection, the MgUserInformation should
 also set the Client IP and Client Agent. Currently, this was only
 happening for the Map Admin.

 * When a web application (Ajax Viewer, Fusion Viewer) makes an http server
 request, it needs to set the CLIENTAGENT parameter.

 * The web tier test pages need to also send the CLIENTAGENT parameter with
 its server requests. We will add editable textboxes for this parameter to
 be consistent with the other parameters.


 Notes:
 * The Fusion Viewer changes will be made to the Fusion vault.

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