Can you share your toml? I set it globally as defined in the docs and not getting any errors or warn
Can you share your toml? I set it globally as defined in the docs and not getting any errors or warnings
KHere you go, redacted some info
wrangler.toml2.17KB
K
W[env.local.version_metadata]
WTOML is great :meowupsidedown:
Kah geeze, thanks! That sorted it 
Dhey, I think this is being addressed, there's a compatibility flag so if you're using something older than
no idea when it will be rolled out to prod, so could be that you're already back to the old functionality, or maybe only next week
2024-09-26no idea when it will be rolled out to prod, so could be that you're already back to the old functionality, or maybe only next week
WDani too fast, yes we're working on rolling out a fix gating this change now
Thmm, anyone know what the size limit is for workers static assets?
TShould be 25MiB
T(Same as pages)
Tah, so also built upon kv?
TYup!
A- yup, we will be adding that soon
- what do you mean by environments? do you mean Workers environments or something else?
Cloudflare Docs
Deploy the same Worker application with different configuration for each environment.
QDoes Workers Static Assets have the same 20k file count limit that Pages does?
LHow do you submit feature requests? You can only through a ticket on a business/enterprise plan? I could ask one of my clients, but I'd rather not bother them.
H#workers-feature-suggestions ?
ADNS and domains aren't my strong suit, so in the case where I want to allow custom domains, that are customer-owned (e.g. I do not own them, my customers do) to be tied to my worker... is the best way Workers for Platforms?
Or could I start out with something simpler / no upfront cost (e.g. a single worker with lots of routes tied to it)?
I know I can have quite a few routes associated to a worker (I think 1,000), it's more the DNS/zone side of things that I am curious about (do I add their domain to my account, then they repoint DNS?) and how it would work from a customer PoV / wanted to check if there was anything I was missing between the two choices.
Or could I start out with something simpler / no upfront cost (e.g. a single worker with lots of routes tied to it)?
I know I can have quite a few routes associated to a worker (I think 1,000), it's more the DNS/zone side of things that I am curious about (do I add their domain to my account, then they repoint DNS?) and how it would work from a customer PoV / wanted to check if there was anything I was missing between the two choices.
HYou need CF for SaaS to allow CNAMEing
HAssuming you don’t have custom logic per zone for your Worker, then you should be able to get away with just one
AAhhh it's hidden under the Workers for Platforms page 
That looks perfect, thank you. And my customers would just CNAME whatever they wanted to (e.g. customdomain.example.com) to my.worker.domain? (going with the easier-looking real-time option)
That looks perfect, thank you. And my customers would just CNAME whatever they wanted to (e.g. customdomain.example.com) to my.worker.domain? (going with the easier-looking real-time option)HYes, though note you also have to add
customdomain.example.comYup makes sense, thank you!
TYes it does!
QBummer.
T?crossposting
FPlease do not post your question in multiple channels/post it multiple times per the rules at #
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.
welcome-and-rules. It creates confusion for people trying to help you and doesn't get your issue or question solved any faster.TAlso I don't think this is the place to advertise period - even offtopic - and you'll like get banned
T@Tim Bless
AIm sorry bro
IWorkers Builds don't use Workers to build (so not V8), they use Cloudchamber (Cloudflare's container platform): https://blog.cloudflare.com/container-platform-preview/
LOk, still from my tests it takes around 10s on average to start the build from when you queue a job.
LThat's very fast and on-par with GHA.
JHello!
Why this simple code not work? (internal endpoint)
The response
I trying with
Why this simple code not work? (internal endpoint)
The response
status_code=200{}I trying with
npm run previewimport type { NextRequest } from 'next/server'
export const runtime = 'edge'
export async function GET(request: NextRequest) {
return Response.json({"a": 1});
}
PIs there plans to support
stale-while-revalidateVary
MHey, I'm curious, how does sending email via Cloudflare works?
IYou can't. The only exception is if you use Email Routing, in which case you can only send email to your own (authorized) addresses and only in response to an existing email coming in.
IThe use-case there is to forward email to yourself or filter email before forwarding it on.
Mokayyyy
MAnd can't I use Gmail Relay with CF Workers? Because I'm using CF Workers as a tiny webhook system and would like to use Trustpilot to send invites when someone closes a ticket (can't use their API)
IYou can send email via an HTTP API through another provider, but you can't send SMTP via Cloudflare Workers sadly, nope.
IAlso just as an addendum in case you're looking online: you might see some past reference to a partnership between Cloudflare and Mailchannels to send email, but that's since ended and can no longer be used.
MYeah because I would've just trusted Cloudflare Workers IPs on Google Workspace relay at this point but bad idea
MMaybe I'll try to reach out to Trustpilot to see if they can allow me to use that feature (it's normally paid)
TAre you use you’re using the experimental flag? What version of wrangler?
BHow are _header files generated with Framework deploy create scripts? I'm using Vue / Nuxt for example, and it's generating this _header file, but I'm not sure how to customize it other than building, then modifying the _header file in dist/ after the fact.
Is there a proper way to hook into that process to add custom headers? Custom headers also don't seem to be actually working this way, I can't get custom headers to show up at all on the pages endpoint. I tried to add x-frame-options and content-security-policy in all manner of ways and it shows up in the dashboard for headers for that deployment, but they don't show on the request in dev tools network for example, so aren't being respected.
Is there a proper way to hook into that process to add custom headers? Custom headers also don't seem to be actually working this way, I can't get custom headers to show up at all on the pages endpoint. I tried to add x-frame-options and content-security-policy in all manner of ways and it shows up in the dashboard for headers for that deployment, but they don't show on the request in dev tools network for example, so aren't being respected.
/_nuxt/builds/meta/*
cache-control: public, max-age=31536000, immutable
/_nuxt/builds/*
cache-control: public, max-age=1, immutable
/_nuxt/*
cache-control: public, max-age=31536000, immutable
Ethose headers only affect static files and not dynamic functions requests, it would be better to add the headers in the code for the functions however that's done in the framework
BThanks, I thought pages were workers basically, and the headers are showing here for example on the page deployment. Do these headers not apply to the actual routed request?
BThis is probably more of a pages question
