___utmvc (three underscores) whose value is computed from a script the page loads and from the cookies the site has already set. Roolink computes the value; you set the cookie and make one activation request.
How to recognize it
The page loads a script from Imperva’s resource endpoint, with a query parameter that starts withSWJIYLWA:
incap_ses_ and visid_incap_. Those are the session cookies UTMVC is bound to.
The flow
1
Fetch the script
GET the _Incapsula_Resource script URL from the page, through your session, with the script headers from your powhttp recording. Keep the body exactly as received.2
Ask Roolink for the cookie
Call
/utmvc with the script body and your session’s cookies as one document.cookie string: every cookie the site has set so far, as name=value pairs separated by ; . The incap_ses_* cookies are the ones the value is bound to, so make sure they are included. Roolink returns the cookie value plus a ready-made cookie header fragment and setCookie line.3
Activate it
Make one If the cookie is accepted, the response clears
GET to the resource endpoint with the SWKMTFSR parameter and a random number, through the same session:___utmvc (it sets it to a with a zero lifetime) and upgrades the session cookies. That is success; the cleared cookie is expected.4
Load the page
Request the page again. It should serve the real content. The session cookies now carry the trust, so you do not need to repeat this flow until the site challenges you again.
Response fields
Request fields
Troubleshooting
The page still shows the Incapsula block after activation
The page still shows the Incapsula block after activation
Confirm the activation request went through the same session and proxy as the page load. If it did, the site is also running Reese84; look for the sensor script and follow the Quickstart.
Roolink answers 422
Roolink answers 422
The script body is not a UTMVC script Roolink can parse, usually because it was re-encoded or truncated. Send it exactly as received.