Can the automatic running of cloudflare worker code while I'm typing be turned off? I can't work lik

Can the automatic running of cloudflare worker code while I'm typing be turned off? I can't work like this when I get basic auth popups every split second and I dont see the advantage of my worker constantly running on each keypress when I can use the Send button anytime I need to run

Mmasd4 Can the automatic running of cloudflare worker code while I'm typing be turned o...

Hello, I’m Allie!•11/29/23, 8:07 AM

You may be able to disable it in the settings, but otherwise, you can develop locally and push

masd4OP•11/29/23, 8:14 AM

I dont see an option for this but I think I may have a workaround.. I have to cause a syntax error and then it doesnt run constantly

masd4OP•11/29/23, 8:14 AM

nevermind it still runs

banbanboi•11/29/23, 8:16 AM

Hi, I am having problem with r2 audio/video file uploaded via presigned URL (PutObjectCommand). It was being uploaded but when we are going to use it via signedUrl(GetObjectCommand) for transcription, file cannot be read for transcription. The get presigned and signed URL are generated through Workers. I tried to download it and played in media player, and still it was unable to play the file. Did I missed something in upload using presigned url ?

but when I upload the file directly in R2, then transcribed the file via signedUrl, the transcription service that we are using are successfully able to transcribed it

Zetax•11/29/23, 5:39 PM

Hey,

I'm currently trying to minimize latency as much as possible. I am currently using Cloudflare hyperdrive with my postgres db + a cloudflare kv cache for my entries, but I am still getting around 100ms latency. Is there any way to reduce this further? I am just running a simple select query and my return size is about 4KB. I attached an image of what my route looks like, and an image of what the respective latency for each operation is. I also attached an image for my db middleware to allow me to use my db in ever call. I know this is not very effective, but almost all my routes use a DB call anyway. Or is there any way to reuse an existing connection?

Unsmart•11/29/23, 5:47 PM

I would remove the cache and remove the 2nd db connection that doesnt use hyperdrive and it should be faster

Unsmart•11/29/23, 5:50 PM

and if theres some reason you really dont want to use hyperdrive for a specific route I would make it where you return only the hyperdrive connection or only the direct connection instead of opening both

UUnsmart I would remove the cache and remove the 2nd db connection that doesnt use hyperd...

Zetax•11/29/23, 5:52 PM

Why remove the cache? It seems to be much faster. Just trying to understand

Unsmart•11/29/23, 5:52 PM

hyperdrive already adds a cache so that would just double cache now

UUnsmart hyperdrive already adds a cache so that would just double cache now

Zetax•11/29/23, 5:55 PM

True, but for some reason the Hyperdrive cache is way slower. It adds about 80ms of latency

UUnsmart hyperdrive already adds a cache so that would just double cache now

Zetax•11/29/23, 6:09 PM

Would cloudflare D1 be better for my use case? I just want the lowest latency possible

Isaac McFadyen•11/29/23, 6:54 PM

D1 would be lower latency in the location where it's created, but it's also SQLite (not Postgres) so anything Postgres specific won't work with D1.

Deo Kumar•11/29/23, 8:12 PM

I am using photon-rs using WebAssembly, and the worker throws

Error 1102: Workers Resources Limit

Error 1102: Workers Resources Limit

, I think it's due to CPU time limit. How can I check the cpu time taken by a fetch handler?

elegant-idn•11/29/23, 9:51 PM

Hi, everyone. Sorry for bothering you, but I need your help
I hosted a static website using Cloudflare workers to optimize the performance
how can I increase the page speed? what should I do, like configuring or anything else?

johnkush•11/29/23, 10:16 PM

I just switched to paid workers plan. Is there something like a safety limit or something, so I don't end up spending big money by a mistake, since it's paid on additional requests as-you-go?

Eelegant-idn Hi, everyone. Sorry for bothering you, but I need your help I hosted a static we...

Cyb3r-Jak3•11/29/23, 10:17 PM

If your site is purely static then I would recommend pages

Jjohnkush I just switched to paid workers plan. Is there something like a safety limit or ...

Unsmart•11/29/23, 10:26 PM

There's no hard limits you can impose, setting up WAF rules to try and block any bot traffic and rate limiting rules to disallow spam would be things you can do to try and ensure expected usage levels.

Normally you could also setup notifications for when you reach a certain request amount but seems due to the billing changes recently made to workers you cannot do this yet with the updated billing model.

crossbeau•11/29/23, 11:57 PM

NuxtJS SSR worker, my code is fetching my dotnet endpoint in azure using a cloudflare origin certificate. I have strict TLS turned on and my nuxt worker is getting 522 errors on request to dotnet endpoint. Do i need to somehow get worker to do an origin pull? If i turn off strict TLS worker goes back to functional

mrwind•11/30/23, 10:17 AM

hi I can't find the api to create a new worker https://developers.cloudflare.com/api/operations/worker-script-delete-worker ? how do i create a new worker from api. Thank

Cloudflare API Documentation

Interact with Cloudflare's products and services via the Cloudflare API

CCyb3r-Jak3 If your site is purely static then I would recommend pages

elegant-idn•11/30/23, 10:23 AM

my website is the build of react. how to deploy it using pages

Erisa•11/30/23, 10:25 AM

https://developers.cloudflare.com/pages/framework-guides/deploy-a-react-site/

Deploy a React site · Cloudflare Pages docs

React is a popular framework for building reactive and powerful front-end applications, built by the open-source team at Facebook.

Will•11/30/23, 11:00 AM

What are your go to rest api framework for cf worker?

Erisa•11/30/23, 11:00 AM

Personally I use Hono

Will•11/30/23, 11:09 AM

Thanks! I’ll try to look at it

Will•11/30/23, 11:09 AM

Still a newbie with serverless concept

Will•11/30/23, 11:10 AM

Does each api call invoke a function and each invocation spawn a worker, is it still preferable to write async?

Will•11/30/23, 11:12 AM

And how about service which have to wait for user input, let’s say an otp service.

User hit api
Api send otp via sms
Api wait for 30 sec for user inputting otp

How does one design such service in serverless? I am open to any solution.

zegevlier•11/30/23, 11:21 AM

Each time a request is made to your worker, the fetch() function is ran with the request information. In workers, multiple requests can share the same isolate (the thing that actually runs the code). You should write workers using async because if you don't do that, you wont be able to do many operations, as they often require async.

I would re-frame the problem here as instead of having the server wait for the user to input the OTP, the server give the user a time limit of 30 seconds to enter the OTP. There are many ways you could do this. You could send the user a JWT that they need to send back that expires after 30 seconds, or you could store the login attempt in a datastore like #d1-beta or #durable-objects.

Zzegevlier Each time a request is made to your worker, the fetch() function is ran with the...

Will•11/30/23, 11:27 AM

Thanks! Now it’s more clear.

I just see durable object, it looks like redis cache

which I think suit the otp use case.

But the jwt method looks more interesting, how does it work? Isn’t jwt token is too long for otp which is usually only four to six digit?

Erisa•11/30/23, 11:28 AM

I believe whats being suggested is the user is presented with a jwt and then within 30 seconds they must return both the jwt and the totp code, which mitigates the need to maintain any state yourself

Will•11/30/23, 11:28 AM

Wow! That’s genius

Will•11/30/23, 11:29 AM

I wish I can be as smart as both of you @zegevlier @Erisa | Support Engineer

Will•11/30/23, 11:29 AM

Many thanks for the help

Original message was deleted

zegevlier•11/30/23, 11:30 AM

I don't think that matters here? Why would you need secrecy for this?

zegevlier•11/30/23, 11:31 AM

oh like that, yea you shouldn't store the OTP in there. Good call, a JTW wouldn't work well here

zegevlier•11/30/23, 11:31 AM

Point still stands though, you just need something that encrypts the information stored

Will•11/30/23, 11:35 AM

This is so much to digest, but I think I get a glimpse of the concern

so basically, the user can give back the the jwt token without having to recieve the otp?

sathoro•11/30/23, 12:01 PM

any thoughts on what can cause

#<Response> could not be cloned.

#<Response> could not be cloned.

? I have error logging with Sentry but I'm pretty sure the stack trace is not accurate -.-

sathoro•11/30/23, 12:04 PM

Sentry says it is coming from this line

await this.state.storage.put(foo, bar);

await this.state.storage.put(foo, bar);

sathoro•11/30/23, 12:29 PM

nvm we had a bug that was trying to serialize a request into DO storage, so Sentry was right this time

frank•11/30/23, 1:46 PM

Hey everyone! Are there any plans to allow query parameters via route patterns without also applying the wildcard to the path? For example:

example.com/page*

example.com/page*

is the only way to support

https://example.com/page?blah=1

https://example.com/page?blah=1

, but it also matches

https://example.com/page1234

https://example.com/page1234

. This seems like a pretty serious limitation.

Ffrank Hey everyone! Are there any plans to allow query parameters via route patterns w...

sathoro•11/30/23, 2:32 PM

it's not possible to match the ?

Ssathoro it's not possible to match the ?

frank•11/30/23, 2:33 PM

It returns an error saying query strings aren’t allowed in the pattern.

Ffrank Hey everyone! Are there any plans to allow query parameters via route patterns w...

Chaika•11/30/23, 2:39 PM

There's been nothing mentioned about them changing soon and Worker Routes haven't changed in a while, that's also a documented limitation:
https://developers.cloudflare.com/workers/configuration/routing/routes/#matching-behavior

Route pattern matching considers the entire request URL, including the query parameter string. Since route patterns may not contain query parameters, the only way to have a route pattern match URLs with query parameters is to terminate it with a wildcard, *.

So I doubt it would change anytime too soon.
It's not the most optimal solution but you could parse the URL in the Worker and check if the pathname equals the one you're looking for, otherwise just passthrough

return fetch(request)

return fetch(request)

the request, wouldn't interfere with anything but would cause Worker Invocations still

Routes · Cloudflare Workers docs

Routes allow users to map a URL pattern to a Worker. When a request comes in to the Cloudflare network that matches the specified URL pattern, your …

Chaika•11/30/23, 2:42 PM

Depending on how your website is setup, you could also potentially take advantage of the more specific matching behavior. If it's something like you want /post?ggg

/post*

/post*

to go to a worker but not /posts?ggg, if you made a route for

/posts*

/posts*

service none, that should be more specific and stop the Worker from running on that path

frank•11/30/23, 2:54 PM

Thanks - just wanted to see if anybody has heard anything about a change. Appreciate the reply

crossbeau•11/30/23, 7:51 PM

is anyone here using Nuxt/NitroServer with Service Bindings on their worker?

Miixms•11/30/23, 8:14 PM

question about the workers.. styandard requests

Can the automatic running of cloudflare worker code while I'm typing be turned off? I can't work lik

Similar Threads

Similar Threads

Similar Threads