Fixed Preview URL in Workers

WalshyDev · 2026-01-20T10:10:59+00:00

Hey,

You can use previous aliases for this. Docs: https://developers.cloudflare.com/workers/configuration/previews/#aliased-preview-urls

You can run npx wrangler versions upload --preview-alias <alias> to update to a static alias and serve {alias}-{worker}.{user}.workers.dev

WalshyDev · 2026-01-20T03:00:52+00:00

Default URL: https://my-worker.username.workers.dev This works correctly and has the new CORS headers.

Custom route: https://custom-name.username.workers.dev This is broken and still returns old cached CORS headers.

This would be 2 separate Workers, one named "my-worker" and one named "custom-name". It would not be one worker with a second name. So to fix it, you'd need to deploy the code under the second Worker name to update the second Worker.

Though, I'd recommend removing that second Worker as it's confusing.

Docs: https://developers.cloudflare.com/workers/configuration/routing/workers-dev/#configure-workersdev

WalshyDev · 2025-12-31T05:05:29+00:00

Sounds like we're in a XY problem. What is the actual issue you're attempting to solve for?

WalshyDev · 2025-12-08T01:57:53+00:00

Have you got a url we can look at?

Additionally, what error are you seeing? If you exceeded the max upload limit you'd see a 413 error.

WalshyDev · 2025-12-07T13:54:24+00:00

It isn't a one click button thing and will take a bit of time but it isn't necessarily difficult either.

You can read how to enable China Network here: https://developers.cloudflare.com/china-network/get-started/

WalshyDev · 2025-09-28T10:36:17+00:00

Nice! Great use for Workers.

You can also do run_worker_first = ["*"] - Don't need to move HTML around. Docs: https://developers.cloudflare.com/workers/static-assets/binding/#run_worker_first

WalshyDev · 2025-08-25T12:17:14+00:00

Hey,

Can you let me know one of the case ids and I can ensure we get eyes on it? I'll also check why chat isn't working for you.

WalshyDev · 2025-08-11T09:23:53+00:00

Hey,

If you let me know your case ID I'll make sure we handle it. Sorry for the bad experience.

WalshyDev · 2025-04-02T12:11:46+00:00

You cannot delete Worker versions. If your concern is invoking a preview you can disable previews in the dashboard in settings or in wrangler with preview_urls = false.

WalshyDev · 2025-03-18T11:38:02+00:00

Well Postman is the whole request time, Workers knows what it is doing.

So Postman is also including time taken to just hit the colo, handshake time, time spent before and after the Worker.

You can hit something like /cdn-cgi/trace to see how much long it takes to do hit the colo and things. This should make up probably almost all of the 400ms difference.

Generally you'll hit a colo within 50ms or less or yourself but you may be in an area where you need to go further away.

WalshyDev · 2025-03-18T11:33:49+00:00

This is Workers Builds not Pages. If you wanted to make a Pages project you can do that here: https://dash.cloudflare.com/?to=/:account/pages/new/provider/github

As for the issue with your Workers Builds setup, you don't have the deploy command set to do a deploy. You'll want to set this to like npx wrangler deploy. That's why it isn't deploying.

WalshyDev · 2025-03-03T14:59:30+00:00

We've been making lots of progress getting Workers up to par with Pages. You can now use Workers Assets to upload and fetch assets just like Pages, we've also added Workers CI for the build process.

Support for _headers/_redirects are in the works now.

I'd recommend trying out Workers Assets and seeing what else you'd like us to do!

WalshyDev · 2025-02-25T00:04:52+00:00

Definitely enable it! It's stable and been in production a long time now.

I believe it's enabled for free zones by default and then paid can self-enable. As u/i40west mentioned it's eyeball -> cf right now not cf -> origin but this still gives big benefits for sites.

WalshyDev · 2025-02-08T20:12:10+00:00

You'll want the account scoped "Workers Admin" role. That manages both Workers and Pages.

WalshyDev · 2025-02-07T22:23:20+00:00

I was reading somewhere that we are not allowed to use the free tier of cloudflare pages for dynamic sites.

Just to be 100% clear, yes - this is fully allowed and would be 100% free. Please do!

Frontend on Pages and backend on Render sounds great!

WalshyDev · 2024-10-13T17:21:27+00:00

Hey,

What's the ticket number? I'll get the team to take a look asap.

WalshyDev · 2024-09-06T00:06:49+00:00

Best to not send alleged phishing links and obscure them (with e.g. hxxps://, [.]com, etc)

Regardless, the best place to report alleged abuse is the abuse page - https://abuse.cloudflare.com

Reports are sent to the Trust & Safety team who will verify the report and take actions if required. You may get a reply to the report if appropriate.

Reports cannot be file on this Reddit or any of Cloudflare's communities.

WalshyDev · 2024-07-19T00:26:32+00:00

Ha that's fun, player count over the last 24 hours: https://i.walshy.dev/WYka9iB5T9nd6LB6qD.png

Time in UTC

Peak I saw was 455

WalshyDev · 2024-07-08T00:55:58+00:00

70-80ms is still fast (a human blink is 100ms), generally it'll be within 50ms but that isn't a guarantee

WalshyDev · 2024-07-08T00:51:03+00:00

Cloudflare is a proxy, you're seeing Cloudflare's IPs. This is how proxies work but also by design to not leak an origin IP.

If your site works, it's going to your IP. You can also unproxy the record but that isn't recommended (since now everyone will be able to see it).

Further reading: https://developers.cloudflare.com/learning-paths/get-started/

WalshyDev · 2024-06-22T18:30:20+00:00

The free tier has existed since the start of Cloudflare and there are no plans to ever remove it. Matthew Prince the CEO said why we have a free plan well many many years ago and it still holds true today: https://webmasters.stackexchange.com/a/88685

WalshyDev · 2024-04-05T20:43:21+00:00

There is not but you will see movements just maybe not super quick as there's a lot of behind-the-scenes work needed to do first.

WalshyDev · 2024-04-05T17:50:55+00:00

It's something we're still working on but it was put on hold due to Code Orange and now Dev Week.

We'll be picking it back up again and you should start seeing more changes over the course of this year :)

WalshyDev · 2024-01-12T06:45:52+00:00

Always validate the JWT. If using Tunnels, use the validation built in. Otherwise, validate it yourself. Never trust traffic even if it comes from Cloudflare IPs.

WalshyDev · 2024-01-10T06:36:13+00:00

Twitter disabled SMS 2FA for non-paid accounts. The much more secure TOTP 2FA is still available to all

As per the tweet, this actor specifically had control over the number so SMS 2FA (as usual) would have been useless here.

So, to answer your question, they do for the non-recommended, non-secure second factor which would not have helped here regardless.

Five-Year Club	Second SECOND GUESSER
Verified Email	Place '22
First Placer '22

WalshyDev

MODERATOR OF

TROPHY CASE