Invalid socket connection url.
Issue #164
closed
Hi, Peter
Thanks very much for the plugin.
I tried the sample script: socket.io-chatserversample.jmx in my test environment.
But the message request is failed.
I used Charles as proxy to catch the request sent from jmeter and find the socket path is invalid.
The jmeter url is like this:
ws://{ipaddress}:3000http://{ipaddress}:3000/socket.io/?EIO=3&transport=websocket&sid=qRQvH9Pm59mAb_POAAFo
But the normal one should be:
ws://{ipaddress}:3000/socket.io/?EIO=3&transport=websocket&sid=NyKjmSMYX-G39mzzAAFp
The path in script is set correctly.
Comments (4)
-
repo owner -
reporter Peter, thanks very much for your explanation.
My script works fine~ Really appreciate this plugin.
-
repo owner Ok, nice. Thanks.
-
repo owner - changed status to closed
- Log in to comment
Hi,
I think you saw http://{ipaddress}:3000/socket.io/?EIO=3&transport=websocket&sid=qRQvH9Pm59mAb_POAAFo in Charles, right? Or really with ws://{ipaddresss}:3000 prefixed, i can hardly believe it.
In case of the latter, please enable debug logging (see readme) and send the log messages of connection setup.
It is normal that you see http:// URL’s in a proxy, because that’s how a websocket connection is set up: it starts with an http connection that is transformed into a websocket connection.
Cheers
Peter