Subrequests are just any network call, you arent billed on subrequests. Service bindings specificall

Subrequests are just any network call, you arent billed on subrequests. Service bindings specifically call another worker and all worker requests are billed regardless of request method which is why calling service bindings has a charge.

UUnsmart Subrequests are just any network call, you arent billed on subrequests. Service ...

Hello, I’m Allie!•4/22/24, 7:05 PM

Though note, because of the architecture of Service Bindings, the bound Worker should already be in memory, and thus calling it is almost like calling a function within your Worker directly(which I suspect is why they might want to make Service Binding calls free).

mihaaai•4/22/24, 7:07 PM

Thanks for the quick reply, hope to also have at least 2 chained requests for free in the future, anyway not sure again about the content of this article https://blog.cloudflare.com/service-bindings-ga being still valid, I understand that many changes have happened since it has been written, but having an api-gatewayapi-gateway like architecture with workers (aka triggering 4+ requests only to have a login token returned) it's too expensive in the long run, only the security from the subworkers isolation might be a perk.

The Cloudflare Blog

Service Bindings are generally available, with efficient pricing

Service bindings are an API that facilitate Worker-to-Worker communication. You can invoke other Workers directly from your code; making it possible to communicate with shared services. We’ll also make it cost-efficient to run multiple Workers.

Mmihaaai Thanks for the quick reply, hope to also have at least 2 chained requests for fr...

UnsmartOP•4/22/24, 7:09 PM

It might be "expensive" for personal use but for companies even 4 requests is still only $1.20/million (+ some cpu time). My work does about $15-20/million requests comparitively on AWS so theres that

Mmihaaai Thanks for the quick reply, hope to also have at least 2 chained requests for fr...

kian•4/22/24, 7:48 PM

https://x.com/irvinebroque/status/1776331933129253290

Brendan Irvine-Broque (@irvinebroque) on X

@sperand_io @elithrar @Cloudflare Two things here:

We are working on (couldn't quite make it for this week) a change where when you call another Worker via a service binding, this won't be billed as a request. (so that pricing doesn't disincentivize breaking apart an app into many Workers) Coming soon.

Twitter

•

4/5/24, 7:31 PM

King•4/22/24, 11:57 PM

Hello everyone, Is it possible to send emails with attachments using the mailchannels plugin? Or has this feature not been implemented?

andrew•4/23/24, 1:45 AM

Is anyone successfully seeing unobfuscated stack traces in the exception output of the real time logs?

andrew•4/23/24, 1:45 AM

i've got upload_source_maps = true upload_source_maps = true and i'm still not seeing them

andrew•4/23/24, 1:46 AM

i'm also watching for exceptions. i'm not merely looking at a console.log of the error.stackerror.stack

andrew•4/23/24, 1:47 AM

This page says stack traces go into open beta on apr 15th. that's in the past, but also pretty recent. so maybe they're just not rolled out yet? https://developers.cloudflare.com/workers/observability/source-maps/

andrew•4/23/24, 2:26 AM

i opened a docs issue here - https://github.com/cloudflare/cloudflare-docs/issues/14194

luna•4/23/24, 6:33 AM

do tail workers generate a new tail worker if they crash to handle their own events or does the chain stop at tail workers?

MMitya There are so many seemingly random errors that show up in Wrangler when developi...

Mitya•4/23/24, 10:29 AM

Anyone from CF able to help here?

dave•4/23/24, 11:46 AM

I know I’ve asked this before.. is there a way to use something like HTTP 100 in a Worker to avoid a 524 timeout?

Original message was deleted

dave•4/23/24, 11:49 AM

Yep I already did that. I just am looking for a more generic solution.

We’re probably migrating off enterprise next month too.

dave•4/23/24, 11:50 AM

@Leo oh wait, is the 100 second timeout only on subrequests and not requests to the Worker itself?

Original message was deleted

dave•4/23/24, 11:52 AM

We’ll be on pro next month so same.

dave•4/23/24, 11:53 AM

If I return even just 1 bytes, that will “reset” my 100 second timeout, right?

Colin Asquith•4/23/24, 12:12 PM

Is there any way to protect the contents of both the Worker and the KV data on a client site? There's some proprietary data we want fast access to, so were using KV to store, but ideally it would be something that isn't public (even though it's the Client's Cloudflare account)

Ddave If I return even just 1 bytes, that will “reset” my 100 second timeout, right?

dave•4/23/24, 12:12 PM

My idea is to try returning whitespaces until the response is ready.

CColin Asquith Is there any way to protect the contents of both the Worker and the KV data on a...

Hello, I’m Allie!•4/23/24, 12:14 PM

Not really. Anything on their Cloudflare account is theirs to see. You could call out to an external API to get the data, but the data will still be in their hands at some point

HHello, I’m Allie!Not really. Anything on their Cloudflare account is theirs to see. You could cal...

Colin Asquith•4/23/24, 12:19 PM

If the external API was also Cloudflare, would it mean it could be very fast? The benefit of it being within the client account is performance and it’s straightforward, there’s some data we would like to add that it’s better if it’s not all public so may look at how to do this or obfuscate it a bit

CColin Asquith If the external API was also Cloudflare, would it mean it could be very fast? Th...

Hello, I’m Allie!•4/23/24, 12:25 PM

Sure, it should be pretty fast. Just keep in mind that any data that reaches the Client's Worker is theoretically something they have access to

naourass•4/23/24, 1:14 PM

I have a question regarding protection against denial of wallet for public worker/function endpoints. In case an attacker found some way to get thousand of ip addresses and used them to send billions of requests to the public endpoint (which is quite common these days), what are some possible approaches/implementations that could turn off your worker automatically if a monthly threshold is exceeded (the threshold could be either the global number of requests or a specific bill amount)?

I believe that in such a scenario for an organisatiton with limited funds, the only thing that you can do is turn off the worker and the availability of its online service (since the bill amount has exceeded you budget or bank account balance). Please correct me if there's other strategies to handle this.

HHello, I’m Allie!Sure, it should be pretty fast. Just keep in mind that any data that reaches the...

Colin Asquith•4/23/24, 1:27 PM

Understood, I know it’s something they would be able to see but for the use case it’s slightly better if they don’t have all of the data together, both to protect it but also for updates so we would control data in one place rather than multiple KVs, I’ll look into it!

Original message was deleted

naourass•4/23/24, 3:32 PM

Oh that would be nice, is there any official documentation for that?

Original message was deleted

naourass•4/23/24, 3:35 PM

It is, but that doesn't mean I wouldn't have to pay the bill if the attacker succeded the ddos...

Nnaourass It is, but that doesn't mean I wouldn't have to pay the bill if the attacker suc...

Beny•4/23/24, 3:41 PM

Actually they take off any legitimate ddoses from your bill

BBeny Actually they take off any legitimate ddoses from your bill 😄

naourass•4/23/24, 3:43 PM

This would be awesome from Cloudflare, but is there any official reference for this that I can share with my collaborators?

Nnaourass This would be awesome from Cloudflare, but is there any official reference for t...

Beny•4/23/24, 3:44 PM

There's only this message from someone with a role in the server here, it's more of a support policy they have than an official "feature" that would be documented.
https://discord.com/channels/595317990191398933/909458221419356210/1041778929654055026

Beny•4/23/24, 3:46 PM

All account analytics are accessible over GraphQL if you wanted to build your own kill-switch too: https://developers.cloudflare.com/analytics/graphql-api/

Cloudflare Docs

GraphQL Analytics API · Cloudflare Analytics docs

The GraphQL Analytics API provides data regarding HTTP requests passing through Cloudflare’s network, as well as data from specific products, such as …

Beny•4/23/24, 3:49 PM

This is on their site too under the DDoS Page

BBeny There's only this message from someone with a role in the server here, it's more...

naourass•4/23/24, 3:56 PM

Thanks a lot for the information

Murmeltier•4/23/24, 8:29 PM

Is workers for plattforms already available as a pay-as-you-go option? Docs are still talking about that happening "on April 16th". :|

MMurmeltier Is workers for plattforms already available as a pay-as-you-go option? Docs are ...

Chaika•4/23/24, 8:50 PM

yep, should be on the left bar: https://dash.cloudflare.com/?to=/:account/workers-for-platforms

Chaika•4/23/24, 8:50 PM

#workers-for-platforms

Chaika•4/23/24, 8:50 PM

workers-for-platforms

CChaika yep, should be on the left bar: https://dash.cloudflare.com/?to=/:account/worker...

Murmeltier•4/23/24, 8:51 PM

omg totally missed that, thx!

Ottomated•4/23/24, 9:59 PM

It seems like there's a pretty drastic deviation from the URL spec that might be a recent change?

new URLSearchParams({ 'a[]': 'b' }).toString()new URLSearchParams({ 'a[]': 'b' }).toString() should be a%5B%5D=ba%5B%5D=b according to the URL spec, but as you can see here it does not escape the param names

Adding the url_originalurl_original compat flag fixes this, but that was changed in 2022 and this has started breaking my apps only recently.

OOttomated It seems like there's a pretty drastic deviation from the URL spec that might be...

UnsmartOP•4/23/24, 10:19 PM

Hmm interesting. Did you happen to change a compat date or any other flags or did it start erroring without any changes on your end?

UUnsmart Hmm interesting. Did you happen to change a compat date or any other flags or di...

Ottomated•4/23/24, 10:20 PM

I didn't even make a new deployment

UnsmartOP•4/23/24, 10:20 PM

I see thats quite bad I will see if I can escalate that issue

Ottomated•4/23/24, 10:21 PM

Although it's possible that the external API that's throwing an error because of this was lenient before

Ottomated•4/23/24, 10:21 PM

so can't pin it down exactly

Ottomated•4/23/24, 10:22 PM

it started happening sometime around the 19th

UnsmartOP•4/23/24, 10:25 PM

Ah I see so the issue might be a result of an api change to a 3rd party unrelated to cloudflare?

kian•4/23/24, 11:33 PM

ada-url was bumped to 2.7.8 2 weeks ago (11/04) so if that has just hit production then there could be a regression there

kian•4/23/24, 11:33 PM

(workerd uses ada-url when using url_standard)

kian•4/23/24, 11:33 PM

kian•4/23/24, 11:34 PM

Looks like it's fixing that regression where it didn't escape them - https://github.com/cloudflare/workerd/pull/2008/files#diff-9890fee256b551c112b657b7d25a5d7003705caddf3df8ff7ef1afe17813b340

kian•4/23/24, 11:39 PM

It's possible that hasn't hit production yet, so you're seeing the bad behaviour from before the ada-url bump.

Subrequests are just any network call, you arent billed on subrequests. Service bindings specificall

Similar Threads

Similar Threads

Similar Threads