What the query parameter tells you
/_Incapsula_Resource is not one resource but one path with several jobs. Imperva's proxy answers it on the protected site's own domain, and the query parameter after it tells you which job you are looking at:
?SWJIYLWA=...in a script tag: the challenge script behind the ___utmvc cookie. On a page that otherwise loads normally, it means the site lets you in but expects the cookie on later requests. The captcha block page can load it too.?SWKMTFSR=1&e=...: the submit path that activates a generated___utmvccookie.?SWUDNSAI=...&xinfo=...&incident_id=...as an iframe source: the captcha block page. Your request did not get the content.?SWCGHOEL=v2&dai=...: the endpoint the captcha page posts its solved token to. A successful post sets anincap_sh_*cookie.
So /_Incapsula_Resource in a script tag on a working page means "checked", while the same path in an iframe that fills an otherwise empty page means "blocked".
The "Request unsuccessful" page
When Incapsula blocks a request with a captcha, the response is a short HTML page with a robots NOINDEX, NOFOLLOW meta tag and a full-size iframe. The iframe points at /_Incapsula_Resource?SWUDNSAI=.... A client that does not render the iframe, such as a plain HTTP client, sees only the fallback text: Request unsuccessful. Incapsula incident ID: ...
- The incident ID is the same value as the
incident_idparameter in the iframe URL. It identifies this blocked request, which is useful when you compare attempts or report a block to the site owner. - The captcha inside the iframe is an hCaptcha or a GeeTest challenge. It needs a token from a captcha solver; the token is posted to the
SWCGHOELendpoint. - After a successful post, the response sets an
incap_sh_*cookie (with a Max-Age of one hour in the example in the Hyper Solutions docs), and the original request can be retried.
Is _Incapsula_Resource malware?
No. It is served from the website you are visiting, by the Imperva proxy that sits in front of it. Browser developer tools, security extensions and antivirus logs show it on every site that uses Imperva Incapsula, which is why it regularly turns up in "is this a virus?" questions. It loads challenge scripts and pages for the site's own bot protection.
The cookies around it
visid_incap_*andincap_ses_*are Incapsula's visitor and session cookies. Theincap_ses_*values are inputs when a___utmvccookie is generated.___utmvcis set by theSWJIYLWAscript check described above.- reese84 is a separate check: a sensor script on a site-specific path that issues a
reese84token. The script and its sensor POST do not use/_Incapsula_Resource. incap_sh_*appears after the captcha block has been solved.
Why request-based clients run into it
The captcha block is Incapsula's answer to a client it does not trust. For request-based scraping that usually means the client failed earlier checks: a handshake that does not match Chrome's TLS fingerprint, a header order no browser sends, a missing reese84 or ___utmvc, or an IP address with a poor reputation. Fixing those is cheaper than solving captchas.
The flow is documented step by step in the Incapsula captcha block docs. The Hyper Solutions Incapsula API generates the reese84 and ___utmvc payloads that keep a session out of the block page.