Can workers responses be cached?

You can cache what a worker responds using the cache API, but cache doesn't run in front of workers so you need to manually check it and it will cost a workers invocation.

Thanks. I've been looking around to see if there are any platforms that allow just the cache hit before the serverless function.

Is your other serverless function expensive to hit? Workers are cheap compared to some other serverless providers, so it might still make sense to put them in front.

Is there a way to make a HTTP request from a worker where the body is gzip encoded? Seems like this needs to be done in userland with an imported gzip implementation. Does workers expose a gzip compress API?

I'm planning for it to be a SPA hosted on Cloudflare Pages and call the API which is hosted on a Worker

i am highly disappointed that https://hello.world.workers.dev/ isn't a thing.

That's my only issue with cf workers.

If hello.world.workers.dev was a thing, i'd say 10/10

Noted

I was using log stream to view worker requests and I'm seeing the REDACTED in a lot of the URLs...is that something Cloudflare is automatically doing to hide the full URL?

Yeah Cloudflare hides what it consider high entropy from logs

The code for how it screens is in the workerd repo if you know C++ https://github.com/cloudflare/workerd/blob/1b5057f2bfcfedf146f6f79ff04e99903d55412b/src/workerd/api/util.c%2B%2B#L220 Examples https://github.com/cloudflare/workerd/blob/1b5057f2bfcfedf146f6f79ff04e99903d55412b/src/workerd/api/util-test.c%2B%2B#L24-L60

Hey guys, before deciding to open or not a thread on #1052656806058528849 , I'd like to ask about the issue here. So my problem looks like this (image attached). I'm not sure what causes the request to be Canceled. I'm using a combination of vk-api and openai-api (chat-gpt). I have no errors in my logs, it just stops producing logs for some reason. You can find my project here if you're interested in details: https://github.com/st4s1k/stas-gpt

awww thank you that helps. interesting!!! ty

qq too in

wrangler dev

any quick workaround to ignore this error

✘ [ERROR] In development, you should use a separate kv namespace than the one you'd use in production. Please create a new kv namespace with "wrangler kv:namespace create <name> --preview" and add its id as preview_id to the kv_namespace "KV" in your wrangler.toml

i dont want to have a dev KV space lol just let me run with prod data (lol prob having everyone ) -> just let me work in prod 😄

just add preview_id with the same id

lol 😄 easy enough thx lol need more coffee

This section of the docs has everything you need: https://developers.cloudflare.com/cloudflare-one/identity/authorization-cookie/ You can take the JWT from the cookie and verify the signature in your Worker.

https://github.com/cloudflare/pages-plugins/tree/main/packages/cloudflare-access is a good reference for the code that'll do that for you using Workers-compatible packages

I think Wildebeest has a modified version that fixes some bugs

It does indeed -

Thank you 🙂 I kept staring at this page then second guessing myself

Any issues with workers atm, getting a workers.api.error.script_not_found 10007 when trying to deploy a worker. The worker does exist

I recall that being a log that occurs when you're on an oldish wrangler version

But the worker still publishes fine, it's just for a message it prints afterwards

just updated wrnagler to 2.13.0 and same

also logged out and login

strange, so our other workers deploy fine, its our one that is being used as a saas fallback and trigger being star/star for the zone