- 1 Manipulating Azure Storage Accounts Using Storage PowerShell cmdlets
- 2 Vapor IO Brings OpenDCRE to General Availability
- 3 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 4 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 5 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
Session Tracking With Apache Page 2
The mod_usertrack module is not part of the standard Apache installation, so to use it you must first add the module to your installation. If you are using a dynamic version of Apache, reconfigure your Apache installation (using configure) and add the --enable-usertrack=shared to the configuration command line. Then, rebuild Apache and copy the module to the modules directory within the installed Apache directory. Finally, edit your httpd.conf file to load the new module:
|Table of Contents|
Adding mod_usertrack to Your Apache Installation
Choosing an Expiry Time
Configuring the Log
Analyzing the Results
The Performance Trade Off
LoadModule usertrack_module modules/mod_usertrack.so
For a static installation, rebuild your Apache executable (again using configure, but after that use the --enable-usertrack option). Because the module is built into the new executable, you don't need to specifically load the module through the configuration file.
With both solutions, be sure to restart Apache, which is best done with apachectl:
$ apachectl restart
Once everything is up and running, you should be able to go ahead with the next section of the configuration. To double check that the new module is correctly installed in the Apache installation, use the -L option (which lists available directives) to httpd and look for the cookie-tracking directive:
./bin/httpd -L|grep CookieTracking CookieTracking (mod_usertrack.c)
Tracking is turned on both globally and on a per-server or directory basis by adding the appropriate directives to the configuration file. The main directive is CookieTracking, which accepts one parameter either "on" or "off." The default is off.
The CookieName directive configures the name of the cookie that will be stored. Because multiple cookies can be active for a given domain, a range of names is necessary to enable identification. In general, the name used should be as descriptive as possible (e.g., MCSLP Tracker).
The final configuration for a directory will look something like:
<Directory "/export/http/webs/com.mcslp"> CookieTracking on CookieName "MCSLP Intranet" CookieDomain .mcslp.com </Directory>