Thanks to the Postman team for this new functionality
Our API has an idle timeout, and expects clients to keep the connection alive. We support both the standard websocket protocol ping/pong mechanism (in our case, client-initiated ping) or an application-level keep-alive API request.
Postman should support enabling configurable client-side pings in the settings (e.g. ping every 10s)
It would be great if we could schedule recurring messages over the websocket as well, although I realize this may be a much less common use-case
Thanks again for the feature, and for taking community feedback.
I need to send Stomp subprotocol subscribe command
It sends the command but fail to subscribe the topic since there is no null character at the end hence I get error that payload is incorrect
Can some one help me how to do send the subscribe command or send Nul character (Byte 0x00)
I’m loving the addition of the websocket client, as I haven’t had a real utility for testing websocket connections, although one issue I have is that new messages are added to the top, and there is no option (as far as I’m aware of, at least) to make it add new messages to the bottom instead. If something like that could be added, it would be wonderful!
That aside, the websocket client is great, and I haven’t come across any other issues with it.
Hi there, I am able to connect to my websocket server using postman. This server accepts binary audio stream and response with speech to text in a json structure. Is there a way in postman to send to my ws server continues audio stream (For example from my local microphone)?
Firstly, Congrats on getting this functionality added! On a quick look, it seems pretty good.
Here are a few issues I’ve faced with it so far:
I don’t seem to be able to name or save my requests, so can’t use them from within a collection.
There doesn’t seem to be the option to use variables at any scope other than global in websockets. It would be nice to be able to define variables within the request scope - like regular http requests.
I can’t remove or modify any of the headers (in particular, I wanted to be able to edit the “Sec-WebSocket-Extensions” header)
(related to the 3rd point) I obtain a compressed response which doesn’t get decompressed before showing it to me, and doesn’t give me the option to decompress it.
I think it would be more intuitive to be able to select previously sent messages under “compose”, rather than having to keep all messages sent and received and delve through them to decide which one to copy, copy it and head to the compose area to send.
The pre-request and test scripts might be a good idea to include here as well. I’d like to be able to pull information out of messages received and use them for regular http requests.
In all, great work so far - being as ubiquitous as you are, you’re always likely to have very demanding users (like myself), but this should help you constantly improve and stay at your market leading position.
To test flows I often need to send the same messages on every connection start. For example a hello, connect instructions etc. It would be cool to “quicksave” message bodys within a websocket connection that can quickly be sent from the list by just clicking them.