Heyyo

I can't get Postgres working

Can someone help me? #1075506748460380310

I cant seem to find much information regarding the limitations of websockets and worker 🤔 Sorry if i have missed something blatant, but does anyone know where i could find such info?

Never mind! Just bad search engine results, so had to scroll for abit

before I build this worker I want to see if anyone has a better idea on this with cloudflare. Right now I have a basic php page that a form post to build the url and then does a redirect to the built url. I was just going to convert the the form action to a worker but wanted to see maybe if there was a better way of doing it in CF without a worker.

can you not do it client side?

it sounds like a client side job unless you need to query the db for data or something

I would think I should be able to do it client side. No query or anything just take the form action build a url and redirect over to them. Would you think I could do it in pages?

Hey folks, I'm hitting the 150char limit in workers logs for logpush. Is that a limit that can be raised?

Probably best to ask in #1041788765783474216 - that's where the team will look 🙂

Thanks!

pretty sure the Worker logging route bug is not fixed 😦

oh it started to log randomly agian

well this is a super weird issue

I cannot use POST on a wildcard subdomain

defining the domain makes it work fine

I get a 522 on the wildcard route when POSTing; known issue?

Oh I figured it out I think..

Was missing the /* at the end of the route.

No clue why GETs were working.

Hey all. Just another quick question. What is the best way to restrict a worker to only being used by another cloudflare pages site? I built an API on the worker where all but one endpoint needs to be restricted to only being used by a cloudflare pages project. The one other endpoint needs to be public. What would be the best way of going about this?

my first thought is that you should check if a request comes from cloudflare (either through ASN or IP address) and then you can safely check the

CF-Worker

header to see what worker is calling your API

i use this in one of my projects like this:

Hey all - I built a small application to explore Cloudflares free tier (https://koryporter.com/posts/exploring-cloudflares-free-tier) and got some really useful feedback on my rate limiting solution using KV being a bad idea because of both the eventually consistent nature and the fact that the write limits are quite low. Durable objects would solve for this problem, but they aren’t on the free tier - anyone solved this before within the bounds of the free tier?

Like this? https://blog.cloudflare.com/unmetered-ratelimiting/

This should do the job, tyvm!

Happy to help!

cannot access key in worker - startup says 'Your worker has access to the following bindings: - KV Namespaces: - FT: . but await FT.get("....") errors with FT is not defined. any tips?

oh - put an env in front of FT - docs out of date