closing old websocket server instances without errors
im trying to implement a ping pong logic combined with an ip rate limiter
i created a Map() like so
trying to account for client attacks where they initiate multiple connection via. dev console. for example running
const websocket = new WebSocket('ws://localhost:8787/websocket');
repeatedly. my ip rate limiter handles the spam. but how can i clean up the previous instantiated server without errors?
ipInfo.serverInstance.close
works as expected
but when client starts a new connection, server gets this error:
any way to get rid of this? i can't seem to find the source of this error.
sorry for wall of postS
sty•118d ago
any help would be appreciated!
ahh got answer from github
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
47KMembers
View on DiscordWant results from more Discord servers?
More PostsCache broken?Since January 11 the build time of our pages application has increased from 1.5m to >6.5m with (AFAIchange pages functions watch directories in wranglerWhen running pages functions locally wrangler watches only the functions directories. Is there a wayBug in flarectl, Cloudflare API docs, cloudflare-go and cloudflare-rshttps://developers.cloudflare.com/api/operations/zones-get
Owner should always have email, id and tError: internal error when replied to a get request with websocket upgrade headers with a websocketIn one of my subdomains, I am redirecting a post request containing websocket upgrade headers to anoIs there an example to create a websocket with a DO for an http/2 request?I am trying to create and return a websocket to a specific request but if the request is made with hMJML on Cloudflare WorkerHas anyone got mjml to work on a cloudflare worker? I have also tried mjml-browser and I get “window