this is much worse

https://github.com/honzabit/durable-limiter I was using this locally and it worked perfectly. but when deploying I noticed it wasn't actually rate limiting requests. so I tried removing the calls to the caching API and then it worked. basically the caching expiring was seeming to not work properly once deployed as a service bound worker

actually probably their caching logic is just wrong since caching doesn't work locally right?

how the heck did they expect caching and rate limiting to work together

ohh they only cache rate limited responses. but I am pretty sure in reality what is happening is non-rate limited responses are getting cached too

Is it possible to return an html page in a different file with workers

without having the html file hosted or having to paste the entire html in the worker

From KV?

you could fetch from a CDN

and cache it

like raw.github.com if you like to live dangerously

That could work but the file gets overwritten often, its a weird case

I could just use pages if I needed it to be available like that

hey you asked for solutions

using pages and having it on github are not exactly equivalent

I also said "without having the file hosted"

well

How often?

depends on what you mean by hosted... if it is not in your worker... and it isn't hosted... what are you expecting?

every deploy basically

so like once a day

or more

KV would be fine, as long as it is less than about once a minute

KV would definitely work but is there no way to just import an html file into the worker?

If not that will do, thank you!

part of the build process you could do that

You can, but then it would be a "part of your worker", which you didn't want.

it's mostly for code readability

its fine if its in the code but as long as I can edit in another file

I mean, once a Worker is deployed, it doesn't need to be readable.