Zach
CDCloudflare Developers
•Created by Zach on 9/5/2024 in #durable-objects
In production, when a client disconnects
Ok. Thank you for the update
10 replies
CDCloudflare Developers
•Created by Zach on 9/5/2024 in #durable-objects
In production, when a client disconnects
@Milan any news?
10 replies
CDCloudflare Developers
•Created by Zach on 9/5/2024 in #durable-objects
In production, when a client disconnects
Right, that would make sense.
10 replies
CDCloudflare Developers
•Created by Zach on 9/5/2024 in #durable-objects
In production, when a client disconnects
Thank you. Yes, there is a close handler. It's based on the websocket chat example cloudflare provides: webSocketClose, webSocketMessage, etc. Again, there is no error locally, it's just in prod. If there is no error locally it's not clear what would be causing this error in prod.
10 replies
CDCloudflare Developers
•Created by Zach on 9/5/2024 in #durable-objects
In production, when a client disconnects
10 replies
CDCloudflare Developers
•Created by Zach on 9/5/2024 in #durable-objects
In production, when a client disconnects
In the wrangler tail for prod but also in the dashboard logs for the worker. In the dashboard it shows as a
Client Disconnected
error. Thanks10 replies
CDCloudflare Developers
•Created by Zach on 8/27/2024 in #durable-objects
Thank you Cloudflare. I have been using
I am using Live Stream and was looking into Durable Objects for WebSocket chat. Since it hibernates I can basically use it as a normal server without the cost of running it.
One question I did have: In production, when a client disconnects it shows a Canceled Error even if the socket is closed properly with a
socket.close()
from the browser when the window closes. Is there a way to prevent the errors from being thrown for normal behavior? Everything works fine and no errors are thrown locally. Everything in the Worker is already in a try/catch
. Thank you!2 replies