you can override it by setting cache rules in the cloudflare dashboard ui for any domain
you 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 tailthere 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
@cachewith 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_SUBREQUESTSIs 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 …
MThis may be a stupid question but how do I find out if my worker runs terminate early? I had issues with some code only being executed partly but I see no indications of that in logs
HIs the event you are looking at an HTTP-event, or something else?
MIt's a sveltekit application and more specifically a form submission which is processed serverside on +page.server.svelte.
The +page.server.svelte code is executed in a cloudflare worker
There I do 2 supabase DB requests + 2 other API calls to some email api
The +page.server.svelte code is executed in a cloudflare worker
There I do 2 supabase DB requests + 2 other API calls to some email api
HIf you don’t use waitUntil, then as long as you receive a response, the Worker will have completed its task
MI don't use waitUntil. The thing is I could not reproduce the issue yet when I had logs trailing with wrangler. The only thing I see is that the last API call did not happen. But is there any way to see this in the cloudflare logs to be certain this is actually the issue?
HDoes it happen if you run it locally with wrangler?
HYou could also log the API response to see that it does go through
DI wanted to put the Worker in the US region so I wouldn't get billed for non-US traffic from Google Cloud Run lol
HIf it is GeoIP-based, then it should always be US anyway
HThough, can't you just prevent Cloud Run from booting anywhere other than the US?
MWill try to do, but is it the only way to find out if my execution was terminated early?
HAssuming that the logs don't show an error, then I don't think it would be getting cut off. Might be something else being skipped in the code
HIf the request goes through, then it has completed execution, so maybe there are some conditions for an API call that aren't being fulfilled
