Cloudflare Developers

CD

Cloudflare Developers

Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news

Join

If you get a status code of 200 back

If you get a status code of 200 back from our API, it means your message has been queued for delivery. Whether or not it actually gets delivered is something you can only determine by watching your inbox for a non-delivery receipt. We will send an NDR if the message bounces for some reason. Otherwise, you can assume it got delivered. We only queue for up to six hours, so that's the maximum time you will have to wait to get an NDR.

I am super new to JS and webtech in

I am super new to JS, and webtech in general (i'm a security engineer flailing helplessly) and am really struggling with how i could implement auth for pages hosted on cloudflare. From what i can tell, i might be able to use workers, but really struggling to find good examples to crib from. The gist of what i'm doing is: I create a page for each user, it contains mostly similar content, with like 2-3 personalization tokens. Nothing fancy, just text, images, videos and one or two embedded components. It seemed smart to just use static pages, but I can't for the life of me get the idea of using workers and middleware to allow users to auth with a magic link, or something else simple like that. I'm really trying to avoid providing basic auth/shared passwords if i can manage it. ...

Strange Glad you got it working though

Strange! Glad you got it working though

``` const cache key c req url

``` const cache_key = c.req.url let response = await caches.default.match(cache_key) if (response) {...

We use Wrangler 3 and the Sentry CLI to

We use Wrangler 3 and the Sentry CLI to push the dist folder generated by wrangler deploy --outdir=./dist to sentry as a release. Some errors do seem to point to the right file, others don't for some reason, also stuff like deduplication and grouping don't always work like we expect to yet.

CPU fail

this either needs some good debugging utilities or serious rework.. suddenly all ci systems failing without reason is not great.

maaan i was about to try out workers

maaan i was about to try out workers with some discord rich presence biz, but i just saw that discord intentionally blocks socket connections from CF workers. a tragedy

I m getting

I'm getting ```bash service core:user:chainfuseapi-plugins-rss2json: Uncaught Error: Dynamic require of "node:stream" is not supported at index.js:1:383 at index.js:18:4350...

has anyone managed to get itty router v4

has anyone managed to get itty-router v4 types working with cloudflare's worker types? the main issue appears to be that both libraries have bespoke typings for Request and Response

can you make a doc issue

can you make a doc issue?

fancy 100 agree there is something in

<a:fancy_100:1092953135552667708>% agree, there is something in the works that means inactive DOs won't get charged

The plugin documentation

The plugin documentation? You're using normal git integration, added the html contact form as is (needs the data-static-form-name attribute to be set to anything), you have the functions folder in your root (not in your output directory) with the _middleware.ts file, you can see in build logs under the functions tab, the middleware listed under route configuration?...

but i get a warning abt cloudflared when

but i get a warning abt cloudflared when running a normal apt update anyway lol

cors issue

how can i fix this issue? "from origin 'http://127.0.0.1:5500' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."

Possible!?!? - Merging Response Headers and Response Body

Can I get some help merging these two functions into one please? ``` if (STUFF) { response.headers.set(...

Crawler Detection in Cloudflare Worker

Can we revisit this? Any way to detect IF crawler using cloudflare worker on PRO plan?

On a Cloudflare Pages site on a custom

On a Cloudflare Pages site (on a custom domain), I'm making an API request to a Worker (on a custom domain) via fetch(), with cache everything and cachettl set. The response object has some Cloudflare headers on it - cf-priority, cf-ray, server - but no CF-Cache-Status. I was expecting to see that to verify if the request was cached or not. What have I missed, please?...