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
Originally posted by PaxxPatriot November 24, 2024
According to the JavaScript socket.io documentation, there is an option to deactivate the addition of the cache-busting timestamp parameter: https://socket.io/docs/v4/client-options/#timestamprequests
The behaviour of the current python-engineio implementation was blocking me from using socket.io with the Skinport socket.io Server.
So my suggestion is to make it possible to disable the addition of this parameter to the initial request URL.
The text was updated successfully, but these errors were encountered:
Discussed in #385
Originally posted by PaxxPatriot November 24, 2024
According to the JavaScript socket.io documentation, there is an option to deactivate the addition of the cache-busting timestamp parameter: https://socket.io/docs/v4/client-options/#timestamprequests
This is also reflected in the JavaScript code here: https://github.com/socketio/socket.io/blob/main/packages/engine.io-client/lib/transports/websocket.ts#L142. It is also disabled by default.
The behaviour of the current python-engineio implementation was blocking me from using socket.io with the Skinport socket.io Server.
So my suggestion is to make it possible to disable the addition of this parameter to the initial request URL.
The text was updated successfully, but these errors were encountered: