Or perhaps

CF-Connecting-IP

instead

Any one know if you can "statically" cache a workers endpoint response? Eg, I have data that only changes 24 times a day. Can I cache the endpoint response to be the same, and that my worker only gets invoked once every hour?

For my use case I want to build my own cache layer over another api to not overload that service with calls which finally result in the same response.

Workers run before the cache and thus cannot be cached. You have to use the cache api inside of workers to cache anything and since its programmatic the possibilities of how to use it are pretty much infinite

and for caching fetch requests:

This is perfect

I'm new to cloudflare. I built a worker, and this script addEventListener('fetch', event => { event.respondWith(handleRequest(event.request)); }); async function handleRequest(request) { const { pathname } = new URL(request.url); if ( !pathname.includes('market-analysis') ) { return fetch(request); } return new Response('Hello, World!', { headers: { 'Content-Type': 'text/plain' }, }); } then i added a route for mydomain.com/* My question now is, Can i read content from a file in the worker, and if not, how can i link it up with a page, and its content. Sorry for the noob question,

Workers don't have access to the filesystem. You have to include the file contents in your script or do a fetch to an external resource

Is it possible to use aws4fetch to implement AWS v4 signature authentication on a backend?

Basically as a server instead of client.

Re: EmailWorkers. Are these OK to use for contact forms?

I see no reason why not. What makes you ask?

I see that in the typescript docs for page functions and the example typescript for a worker have different return types. Is there a reason for this? Which should I use?

Neither of them explicitly define return types, if that is what you mean?

sorry you're right not return types but yeah, they use different types

if you're using Pages Functions you use the Functions syntax/types

if Workers, the Workers syntax/types

That's because

PagesFunction

passes everything into a single

ctx

object, while the

ExportedHandler

supports the many handlers that a Worker can run:

fetch

,

scheduled

,

queue

, etc.

They use a different syntax, so they get different types

OK, are both capable of using queues?

If you want to use the

ExportedHandler

type while writing Functions, then you can use Advanced Mode

Functions is capable of pushing to a Queue, but it is not capable of being a Queue consumer

Got it, and this is maybe a dumb question but if I'm using Pages can I still have a Worker that isnt a Function, to consume a queue?

Yup, though that won't be deployed automagically by Pages CI(the Github/Gitlab integration).

I see, so even if they are all in the same repo, I'd need to add a build step to use I think wrangler cli to deploy the worker from github actions?

Not necessarily. You can add a extra step in your Pages build command that deploys the Worker, it just won't happen automatically

OK I think I'm getting it thanks, one of those steps could be the wrangler command to deploy the Worker?

Yup

Cool I'll give it a try