SI noticed that requests are cached with workers by default, how does that work? Is it at the browser level or with cf?
Scan I get some links
CThere's always persistence between requests to the same isolate. The thing is each metal/machine has its own isolates, each colo/cf dc has its own metals, some Pops have mutiple colos, and besides your own connection persistence there's no routing preference to go to a machine that already has your isolate spun up on it
SCloudflare respects the origin web server’s cache headers in the following order unless an Edge Cache TTL cache rule overrides the headers.
HThough note that your Worker cannot do IO in startup mode
HSo you can't fetch stuff or interact with Bindings
SI don't know about other langs, but I found very interesting way around (for rust)..
if we have files predefined, then we can load the content at compile time
example:
this will read the file content and we store it in memory
if we have files predefined, then we can load the content at compile time
example:
this will read the file content and we store it in memory
Scan someone help with this please
HYeah, though too, if you can do that, you should be able to precompute the result too, depending on what you are doing
Dyou can override it by setting cache rules in the cloudflare dashboard ui for any domain
SI am looking for some docs which says how to content is cached
I have a worker deployed, which makes post requests and gets json as response which is cached I think
but I want to know if it's cached in the browser or the local server or is it cached for all workers like kv
I have a worker deployed, which makes post requests and gets json as response which is cached I think
but I want to know if it's cached in the browser or the local server or is it cached for all workers like kv
Dwhich makes post requests and gets json as responsePOST requests aren't going to be cached by default.
S
Slooks like it's cached
S1st response took 2.4 sec then it was ~50ms
DI can't tell if the your browser is caching or not from that screenshot
Dyou can do
wrangler tail to see if your worker is being hit or notSthere is no implementation for caching
Srunning without remote flag takes around the same time for each req
Safaik egress is cached
Sbut at what level
IGraphQL requests are cached by default with some GraphQL servers so if it's caching a GraphQL POST then that's probably why.
I(as in, not at the CDN level, it would be at the Worker/GraphQL library level)
Swhat's worker level? The local server?
II assume you have a Worker serving GraphQL requests there?
Snope, the back end is our graphql server, it does not have any caching implemented for worker
Syes
IWhat GraphQL server is it?
IFor example, Apollo server sometimes has caching enabled by default.
IIt's definitely not the CDN caching it unless you have specifically told the CDN to cache it somehow.
Swe are making some thing like apollo server
SIIt looks like you have a cache of some sort there?
Syes that's different thing
Sit's entity cache
Syou can use
@cache operator in the schema, which caches specific parts of the schemaSwith specified ttl
SI thought you were referring to https://github.com/tailcallhq/tailcall/blob/main/cloudflare/src/cache.rs
but anyways even that code is not used, it was recently introduced, the screenshot is quite old
but anyways even that code is not used, it was recently introduced, the screenshot is quite old
GThe comments i get are for another worker that is running, the one under fev is silent/
DIs it possible to force smart placement to be on?
GWhat is that?
Gno one is particualrly talking to anyone
AHey all, question. From the behavior I'm seeing, smart placement does not count requests to R2 as "subrequests", and therefore is not getting past the
Is this expected behavior?
INSUFFICIENT_SUBREQUESTS placement status.Is this expected behavior?
CWhat do you mean by force? If you set it then it should be on. You can’t force a location though
SI'm working on a small project i.e.., A user can install there subdomain path form main domain
ex :- hashnode.com //main domain
sunilkumar.hashnode.dev //sub domain like that
we have personal access token to access particular details of a user and later we need to check like what are available domains on the user and we need to take which domain you need to install like that
by using workers how can i achieve this problem .
can anyone help me out the best way to achieve and also some insights and resources
@andrew | as1003
ex :- hashnode.com //main domain
sunilkumar.hashnode.dev //sub domain like that
we have personal access token to access particular details of a user and later we need to check like what are available domains on the user and we need to take which domain you need to install like that
by using workers how can i achieve this problem .
can anyone help me out the best way to achieve and also some insights and resources
@andrew | as1003
MHi.
So, I have used the default workers example for caching POST request: https://developers.cloudflare.com/workers/examples/cache-post-request
The scenario is the following:
So, I have used the default workers example for caching POST request: https://developers.cloudflare.com/workers/examples/cache-post-request
The scenario is the following:
- User lands on the page and the POST request to the endpoint is made via XHR (AJAX) call. The
isCf-Cache-StatusDYNAMIC
- Same user hits this endpoint with the same payload and CF returns the cached result. The
isCf-Cache-StatusHIT - When another user from a different device hits the same endpoint, CF still hits the origin.
Documentation for Cloudflare Workers, a serverless execution environment that allows you to create entirely new applications or augment existing ones …
