WURFL InFuze Module for HAProxy: User Guide
This document is aimed at developers and system administrators who intend to install and configure the WURFL InFuze Module for HAProxy on Unix, Linux, and other Unix-based systems.
In order for the Module to work it is ESSENTIAL that the
libwurfl library is installed on your system.
libwurfl is provided in your Customer Vault/FileX.
WURFL device detection is included in the HAProxy source code from release 1.7-dev6. You are required to download and compile the
HAProxy source code including WURFL device detection: please refer to the HAProxy documentation for building instructions. You will need the WURFL InFuze C API (libwurfl) installed on your system at compile time
(refer to "Installing libwurfl" above).
To enable WURFL device detection, you will need to add
USE_WURFL=1 to your HAProxy compile command as shown below:
$ make TARGET=<target> USE_WURFL=1
WURFL_DEBUG=1 can be set to increase logging verbosity.
The following are supported WURFL directives (see doc/configuration.txt in your HAProxy source tree):
- wurfl-information-list [
](list of WURFL capabilities, virtual capabilities, property names we plan to use in injected headers)
(character that will be used to separate values in a response header, ',' by default).
(Sets the WURFL caching strategy)
- wurfl-patch-file [
](Sets the paths to custom WURFL patch files)
Sample configuration file:
global wurfl-data-file /usr/share/wurfl/wurfl-eval.xml wurfl-information-list wurfl_id model_name is_tablet #wurfl-information-list-separator | ## LRU cache wurfl-cache-size 100000 ## no cache #wurfl-cache-size 0 #wurfl-patch-file <paths to custom patch files> ... frontend bind *:8888 default_backend servers
There are two distinct methods available to transmit WURFL data downstream to the target application:
All data listed in wurfl-information-list
http-request set-header X-WURFL-All %[wurfl-get-all()]
A subset of data listed in wurfl-information-list
http-request set-header X-WURFL-Properties %[wurfl-get(wurfl_id,is_tablet)]
Based on the configuration above, the
X-WURFL-All header value will result in something like
(all wurfl informations configured in wurfl-information-list, in the same order as listed, separated by a comma)
X-WURFL-Properties header value will result in something like
(only wurfl_id and is_tablet informations, in the same order as listed in
wurfl-get() call, separated by a comma)
wurfl-information-list configuration directive may include:
wurfl_idContains the device ID of the matched device.
wurfl_root_idContains the device root ID of the matched device
wurfl_isdevrootTells if the matched device is a root device. Possible values are "TRUE" or "FALSE"
wurfl_useragentThe original user agent coming with this particular web request
wurfl_api_versionContains a string representing the currently used Libwurfl API version
wurfl_infoA string containing information on the parsed wurfl.xml and its full path
wurfl_last_load_timeContains the UNIX timestamp of the last time WURFL has been loaded successfully.
wurfl_normalized_useragentThe normalized user agent.
wurfl_useragent_priorityThe user agent priority used by WURFL.
Capabilities and virtual capabilities
Refer to WURFL capabilities for all capabilities and virtual capabilities names.
© 2018 ScientiaMobile Inc.
All Rights Reserved.
NOTICE: All information contained herein is, and remains the property of ScientiaMobile Incorporated and its suppliers, if any. The intellectual and technical concepts contained herein are proprietary to ScientiaMobile Incorporated and its suppliers and may be covered by U.S. and Foreign Patents, patents in process, and are protected by trade secret or copyright law. Dissemination of this information or reproduction of this material is strictly forbidden unless prior written permission is obtained from ScientiaMobile Incorporated.