You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I'm experiencing CORS issues specifically during Socket.IO reconnection attempts in Firefox, while Chrome works fine. The initial connection works in both browsers, but Firefox fails to reconnect with:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:1337/socket.io/?EIO=4&transport=polling&t=htb75obx. (Reason: CORS request did not succeed). Status code: (null).
Behavior
Initial connection works in both browsers
When disconnecting:
Chrome reconnects successfully
Firefox fails with CORS error
The error only occurs during reconnection attempts Questions
Is there a known issue with Firefox handling Socket.IO reconnections differently?
Are there Firefox-specific CORS settings I should consider?
Could the ws:// protocol in the client (vs http://) be causing issues?
Any insights would be greatly appreciated! Let me know if I can provide any more specific logs?
Description
I'm experiencing CORS issues specifically during Socket.IO reconnection attempts in Firefox, while Chrome works fine. The initial connection works in both browsers, but Firefox fails to reconnect with:
Setup
Client (localhost:3000)
Server (localhost:1337)
Versions
Behavior
Initial connection works in both browsers
When disconnecting:
Chrome reconnects successfully
Firefox fails with CORS error
The error only occurs during reconnection attempts
Questions
Is there a known issue with Firefox handling Socket.IO reconnections differently?
Are there Firefox-specific CORS settings I should consider?
Could the ws:// protocol in the client (vs http://) be causing issues?
Any insights would be greatly appreciated! Let me know if I can provide any more specific logs?
I checked the documentation https://socket.io/docs/v4/handling-cors/ here but did not manage to solve it my self.
The text was updated successfully, but these errors were encountered: