aboutsummaryrefslogtreecommitdiff
path: root/castle-search/test/google-links.test.ts
AgeCommit message (Collapse)Author
18 hourscastle-search: resolve Google links lazily, in Chrome, not eagerly over ↵HEADmasterIgor Soarez
plain HTTP The Node-side resolver sent one curl-like request per result with no cookies, JS or browser; Google answers that with its 'Verifying your request' countdown after a handful, and the testing itself triggered it. A click or direct navigation in Chrome redirects at once (measured). Search now leaves Google links wrapped and prints the breadcrumb Google shows for each. castle_cdp_resolve follows one wrapped link in a Chrome tab when the agent picks it, accepts only google.com/goto?url=<token>, and reports the verification page instead of waiting it out.