Manually verify your CLE configuration

We are already working on improving the debugging capabilities of the Cookie Lifetime Extender verification. Until improved error messaging is implemented, please find a guide on manually checking the status of the verification and possible reasons here.

Installing Postman CLI

For the manual verification check to be working, you need to install the official Postman CLI. You can find the guide here.

Sending the Postman request

Copy/Paste the codeblock below, replacing "<yourwebsitedomain> and <hash> with the values from your DCP CLE settings page.

postman request POST 'https://<youwebsitedomain>/<hash>' \
  --header 'Content-Type: application/json' \
  --header 'Cookie: jts-rw={"u":"91409167904637152936318"}' \
  --body '{
    "client": {
        "clientTimestamp": 1743756071564,
        "domain": ".<yourwebsitedomain>"
    },
    "cmd": {
        "key": "setcookie-itp-proxy",
        "data": [
            {
                "name": "jts-rw",
                "value": "{\"u\":\"91409167904637152936318\"}",
                "exdays": 17280000
            }
        ]
    }
}'

Interpreting the response

The responses to this request will be HTTP Response codes

Response Code	Meaning
200	The redirect worked, cookies were set with correct duration! You successfully configured the CLE. 🎉
404	The redirect is not working and the request is ending up on a page that is giving back "404 - Not found".