In the interests of being the first to report a bug (because that’s what I do for a living), there aren’t any upper bounds to the Settings values, and if you type enough digits then it ends up displaying as Infinity:
Postman crashes if you try to submit with this value. But now I have a way to reliably crash Postman if I want; which, as a tester, maybe I do
Feedback #2: The search/filter in the message pane is excellent :chefs-kiss: but would be even better if it could be given the same power as the other search fields in Postman, i.e. case/regex matching.
Thanks a lot for bringing this feature to Postman. It is not working with Sec-WebSocket-Protocol request, the handshake itself fails as “Server sent a subprotocol but none was requested” but the same works with other browser extensions like “WebSocket king client”
I have a C# .Net Core 5 WebSocket server using the websocket-sharp nuget package.
I have a C# client successfully sending and receiving websocket messages to the server.
I’m v new to websockets and the c# library I’m using, so might well be missing something obvious, but the fact that the client in C# works makes me wonder what that could be?
Could you confirm which platform you’re using - The native Postman App or the Web Version?
If you’re using the Web Version, do you have the latest Postman Agent installed and have that selected in the UI?
You may have Auto Select enabled which might be pointing to the Cloud Agent, you can check this in the UI, on the menu bar at the bottom right of the view.
A screenshot of the full app view will also help us to know what’s happening in front of you
@mailmaxxx It looks like you’re trying to send BALUS as a URL parameter when creating the connection. You need to first connect to your WebSocket endpoint, then you can send messages:
type in ws://localhost:5555/tk for the URL
click connect
once connected, add you messages in the textarea below and click send
@arlem In my case I am not sending any param and properly requesting the WAMP subprotocol. The WAMP router replies with the subprotocol requested but Postman fails as if I never requested it. Any ideas?
@aramallo My guess is that we’re not supporting that sub-protocol yet, but I’ll leave it to the engineering team to confirm! If we don’t support it I’ll add it as a feature request.