Well, that feature should be released in production mode ASAP, I need to save socket connections in my teamās collection!
1 Like
Nice and welcomed feature!
But i got a little problem with it.
lets say I have a socket server with a namespace in it:
URL: http://localhost:3001/mynameSpace
io.of("/mynameSpace").on('connect', function (socket) {
console.log("Connected!") //Reached!
socket.on('disconnect', function () {
console.log("Disconnected!")
})
socket.on('Test it!', function () {
console.log("test it") //Not Reached ):
});
})
How can i emit messages for it to reach the socket.on('Test it!,ā¦ scope?
Tried using few args, one arg, Text format, JSON format.
iām using Socket.IO version 2.x.
BTW, if iām not using namespace i can use Raw mode, send a text message with this format:
42[ātest itā,{āFooā:āBarā}]
To this URL:
ws://localhost:3001/socket.io/?EIO=3&transport=websocket
and itāll work, BUT i cannot use namespace with this method.
Please help!
Thanks!
I am facing the same issue when there is namespace. Based on comment by @udit, namespace can be added in URI. I still canāt get what custom path in handshake path means.
Ok, I solved my problem.
I missed the part where you can specify the event name in the text box to the left of the Send button.
If youāre passing a JSON, make sure youāve chosen a JSON format message.
Hope itāll help you too.
I would love to see basic authentication for wss. Thank you!
+1 having a saved list + the ability to export them etc would make this feature mega
Could you please help me achieve the following Altair functionality in Postman:
What I currently see is that I can use just ws for Raw Websocket Requests and wss for Socket.IO but just using GET and not POST and also have no idea how to properly use the request body 
Please add the save websocket request feature(enable save button) as soon as possible. Without it, I donāt see much use of this feature.
Postman does not receive responses when running ws://localhost:3001
Set-up:
Running WebSocket API in localhost:3001.
Requests made from Postman to the above are always successful and execution continues up to the āsendā command to return the results. Unfortunately, the response is never received in the postman console:
However, when the same codebases is deployed to AWS, it works perfectly, as the console reveals the successful response below:
I have also attempted to connect from a Firefox, Brave, Chrome console request. The results there are the same. Successful send, no response.
Logical deduction tells me my iMac is blocking traffic. Would this be the case? Or, am I missing a configuration step in my Postman set-up?
Jay
Did the āWebsocket supportā supports Authentication particulary the āBasic Authā?
I was able to connect to websock using RAW but the app crash as soon as I try Socket.IO it crashes. Any idea what i am doing wrong?
Sorry new here, but was wondering if there is any way to define the socket config.
Ex:
const socket = io(namespace, {
path: ā/ioā,
withCredentials: true,
});
Mainly with the withCredentials, that is because it captures the cookies set by the server āAuthorization Bearer tokenā And it gets push forward when the socket is connected and appended to the header.
In my own application, I have other users log in through regular HTTPS, once they get authenticated, the UI will start using SocketUI for the rest of the communication passing the credentials on every request.
WebSockets in Postman are awesome! However I do have a feature request: Allow a user to manually fragment frames (or enable it after a certain number of bytes in a message).
This could be really useful beyond just sending and receiving on WebSockets. We have an event monitoring stream using WS and I would love to be able to use postman to make sure our responses are:
- valid (schema validation)
- timely (events generated by other sources/APIs)
- accurate (e.g., apply a test to a response that matches a filter to see if itās got data in the range or with values we are expecting).
- Duplicate Tab option is not working for websocket as expected, it creates new blank connection tab.
- Please provide option to save websocket responses/messages (with timestamp).
- Enable save option, make websocket requests part of collection, so user can load test.
- Pane view options are not working for websocket tab
Thank You.
It would be also great to have functionality to capture cookies from Postman Interceptor to reuse it in WebSocket request. Just like it works for regular http requests.
1 Like
Websocket Saved messages if they are made global could be then used across different websocket requests.
Can i create API Documentation from a websocket collection?
@cryosat-specialist-6 Yes you can. Please check out the latest release where you can save websocket requests in a collection and create basic documentation.
I found this feature to be extremely useful. Iām having a hard time finding an alternative beside writing my own test client. I have one problem that I canāt get over. I now have to have a workspace to use this feature. I have to sign in to have a workspace. I donāt have a way to turn off data sync if I sign in. Iām not going to sign in until I can control what syncs to your servers.
I donāt have a need for granular control. All I need is an on/off switch for syncing.
1 Like