Contains the URL of the referring document the client came from. It may be used to feed statistic tools.
Technically, this cookie will be stored for 30 days. However, FIT removes the cookie upon the next request, as it is only needed to provide the missing
Referer header when the Detection Page is used.
Makes technical information about the user’s Web browser, like viewport width and height, available to the server software. The cookie does not contain any tracking information.
This cookie will be stored for 30 days
Format: at least 16 parts ending in ‘
:‘. The system parts in the following order are:
2). The value must be a positive number <= 30. This is necessary for creating sharp images for higher-density clients.
screen.widthvalue that can be used to improve the
screen.heightvalue that can be used to improve the
history.pushState. Contains the information whether or not the client supports
history.pushState(). This is needed to determine whether partial page loading is available.
All other (user) parts are added by the JS Detection API and have the format key=value.
For the detection page to be sent, your request needs to meet the following criteria:
fitdetectionmust either not be existing or have the wrong version
apfailmust not be in the request url
mmust not be in the request url
X-Requested-Withheader must not be
X-mozheader must not be
X-Purposeheader must not be
Acceptheader must contain
jsmust be true
client/botmust not be true
include-patternmust match the request url
exclude-patternmust not match the request url
You can enable the detection page in the
ress settings in your config.xml:
<config> <ress> <detection-page /> </ress> </config>
The detection page config option offers multiple parameters.
title: changes the html title of the detection page.
include-pattern(optional): may contain a regular expression pattern.
exclude-pattern(optional): may contain a regular expression pattern.
title parameter replaces the default value used as title for the detection page. The value must be a non empty string. The default is
FIT14 Detection Page.
The following example shows how to generate a detection page with a different title:
<config> <ress> <detection-page title="Different Title" /> </ress> </config>
titleattribute results in an empty
titleelement, creating an invalid document to be output.
include-pattern must match the client request URL to allow FIT to respond with the detection page. If specified, it replaces the default, which allows any URL (think
exclude-pattern must not match the client request URL to allow FIT to respond with the detection page. If specified, the exclude pattern will be added to the default exclusions (
Requested URLs that match both include and exclude pattern will be excluded from detection page responses.
The following example shows how to prevent FIT from responding with the detection page for every request containing
/downloads/ in the URL:
<config> <ress> <detection-page exclude-pattern="/downloads/" /> </ress> </config>
ajax parameter replaces the default behaviour of loading the main content by an own request with an advanced mechanism to ensure the display of the actual content without having to reload. By serving the detection page within the same request, the original referrer is kept intact and can be used transparently.
fitreferreruseless, hence it will not be created.
The following example shows how to generate a detection page without requiring a reload:
<config> <ress> <detection-page ajax="true" /> </ress> </config>
<config> <ress> <detection-page script="fit://site/conf/js/script.js" /> </ress> </config>
In the unlikely event of the detection page not working correctly the content will be loaded with the URLMark
If enabled, the detection page can cause a HTTP redirect before the actual content is loaded.
The hardware display size of desktop clients is calculated from the detected viewport and pixel density.