Tag | Description | Availability |
---|---|---|
<WurflIISServer> | Aggregates the WURFL engines configurations for local IIS Server Context:`root` Type:`mandatory` |
1.7.0.1 |
<WurflIIS> | Contains the configuration for a subset (WURFL engine) of the web sites hosted by local IIS Server Type:`mandatory` Context:` Attributes: `name`: a symbolic name for the web sites managed by the nested configuration for logging purposes `site`: a regex representing web site URLs managed by the nested configuration. WURFL Isapi filter will check the HTTP Request against this regex to determine which WURFL engine will manage the incoming HTTP Request. |
1.7.0.1 |
<WurflRoot> | Defines the location (path) of the WURFL data file. Type:`mandatory` Context:` Value:: the full path of the WURFL data file |
1.6.4 |
<WurflUpdater frequency="DAILY"> | Allows seamless update of the WURFL Engine with new data downloaded from Scientiamobile.
The tag ` |
1.8.3 |
<WurflPatch> | Adds one or more custom patch files to the WURFL repository. Type:`not mandatory` Context:` Value:: the full path of patch file |
1.6.4 |
<WurflEngineTarget> | `This configuration option is deprecated and will be removed in a future release.` | 1.6.4 |
<WurflCache params="100000">single_lru<WurflCache> or <WurflCache>null<WurflCache> |
In order to increase performance while processing real HTTP traffic, we suggest setting up an `LRU` cache.
The `LRU` caching strategy will speed up lookup operations on processed User Agents by keeping them in an LRU map.
By default the cache will be set to 30000 entries, which accounts for 7 to 10 MB of additional memory usage.
Specific concerns regarding memory usage apart, users are advised to size their cache generously (100,000 or more) to increase performance.
For more information, please see [LRU Cache Mechanism](http://en.wikipedia.org/wiki/Cache_algorithms#Least_Recently_Used). Type:`not mandatory` Context:` |
1.6.4 |
<WurflRequestCapability> | Defines one or more WURFL Static/Virtual Capabilities values to be injected in the
Request as HTTP headers. Type:`not mandatory` Context:` |
1.6.4 |
<WurflUserAgentPriority> | `This configuration option is deprecated and will be removed in a future release.` | 1.6.4 |
<WurflLogHeaderInjection> | Logs header injection activity Type:`not mandatory` Context:` Value:`true`/`false` (default value is `false`) |
1.6.4 |
<WurflDoNotProcessUrl> | URLs blacklist section: all URLs matching the contained regex will be excluded from wurfl headers injection. Context:` |
1.7.0.1 |
<WurflProcessUrl> | URLs whitelist section: all URLs matching the contained regex will be injected with wurfl headers. Context:` |
1.7.0.1 |
<WurflUrl> | An url to match Context:` Value: the regex representing the url Attributes:`name`: a symbolic name for the URL, for logging purposes |
1.7.0.1 |