(but that's a 400 not a 401, and not on the normal endpoint)
(but that's a 400 not a 401, and not on the normal endpoint)
IYeah I realized that after I sent it 
IThere, deleted.
I1101200 looks like:
Turnstile was used on a domain that was not allowed for this widget to be used on. Ensure that the domain Turnstile is intended to run on is allowed in the widget configuration.
Berm we work on it togeather
Bhe gave me the task he couldnt do
Bwe want to secure our worker to slow down scrapers
RHuh my
Same exact code from my laptop works but when I deploy it up it doesnt fire
data-callback isnt being called.Same exact code from my laptop works but when I deploy it up it doesnt fire
HAnyone ever get an Invisible Turnstile?
HAre those interactive?
HLike where you have to click them?
HHuh... I sometimes get an interactive challenge on a challenge page, where nothing is visible, but it will stay on that page until you click where the widget would normally be
HIt doesn't happen every time tho, so I haven't been able to capture it
HBecause the website it is on always triggers a challenge for me. In addition, the page does not advance until I click where the checkbox normally is, but then immediately redirects to the actually page when I click
HNo, it’s the WAF Challenge page
HThe “Verifying you are a human” page
HOh, gotcha. But no, no UI is rendered, where the widget should be
HHuh… still wondering why it is sporadic tho..
Bi did it
Bi fixed the thing!
Bnice library
DQuestion: I am currently hitting the 10 widget limit for Turnstile. Is this limit per user? For example, I manage several websites that are not yet added to my Cloudflare account. Would adding these websites to my account help remove the 10 widget limit?
DOk so getting a Pro plan would remove the limit? I am trying to find some clarity regarding Turnstile on the CF website but it's not very clear to me
DOk that seems a bit harsh
Sis there any API or key I can use to validate cf_clearance cookies?
SI am trying to use a worker to implement more fine grained rate limiting and turnstile challenges
Swould like to be able to validate a cf_clearance cookie and let requests with valid ones pass through the worker, similar to how managed challenge work
SI ve seen this thing in actions
Ssorry, what do you mean by that?
SI Have seen a service that does verify clearance for json endpoint , so yes its possible
Sit is.
Swell can json endpoints be protected by waf ?
Sthen it is possible
IIt's not possible to do it in your Worker though.
IIf the cookie is rejected the Worker will never be invoked so will never know it was rejected.
IYou can certainly protect a Worker, just not validate in the Worker.
Sdoes the turnstile cf_clearance cookie mean that the request.cf.botManagement.js_detection.passed field will be set to "true"?
Sit would be helpful if once a challenge or turnstile is passed that field was set to "true"
Cit's best practice to store a turnstile secret key in the wrangler.toml secrets space right?
ISecrets are not stored in wrangler.toml (they're manually added via
wrangler secrets put), but yes.IWrangler.toml is plain-text and non-encrypted, so secrets are better for storing keys.
Cahh ok
Cthanks!
Calong those lines, how do I access a secret in a page function? it doesn't seem to be passed in through the env variable through the fetch request
Cat least, when I iterate through the env object, it doesn't seem to have my secret
HHave you tried accessing the secret directly, rather than iterating?
Cyeah I get null when I log it. maybeeee it's because CF obfuscates my secret when put through a console log but my turnstile is failing so I'm trying to debug through that
CI'm accessing it as env.SECRET_KEY (I know the env variable is being assigned correctly because I have a KV binding that works from it)
