You are viewing the documentation for Blueriq 17. Documentation for other versions is available in our documentation directory.
The AQ_GetHeaders service can be used to map one or more HTTP headers from the session and place them in specified attributes in the profile.
Parameters
| Name | Description | Type | Required |
|---|---|---|---|
| Headers | Specify the technical header and the attribute to which the value is transferred. | Multivalued - Key value pair - Module element - Attribute | Yes |
Do not pass any values that are (database) id's, privacy sensitive data or otherwise possibly harmful data as those values are visible to users and can be changed by users.
To be able to map HTTP headers to your profile, two steps are required:
- Model a service call of type AQ_GetHeaders and specify in it which headers need to be mapped to which attribute,
- Configure your runtime as described in Custom HTTP headers setup.
Example AQ_GetHeaders service
Exit events
Name | Description | Type |
|---|---|---|
| OK | When the AQ_GetHeaders service executed successfully. | Continue |
| MappingFailure | When at least one of the requested headers was not available in the session. The header(s) that were not available can be found as a warning in the log file. | Continue |
| NothingToMap | The operation had no effect, because no headers were saved in the session. | Cancel |
Overview
Content Tools