I’m trying to make it work with SignalR and c#, I was following a tutorial to test this from MS: https://docs.microsoft.com/en-us/aspnet/core/tutorials/signalr?view=aspnetcore-5.0&tabs=visual-studio
And it connects successfully using wss endpoint:
However none of the messages pass trough, and when I open it from webBroswer client (same client from the tutorial), and debug the code, it only shows 1 client connected (the browser one) ;/
Edit:
As well verified from .NET code, that connection is not invoked, as there is a method in hub that can be accessed public override Task OnConnectedAsync() which does not get called
Edit2:
Wrote separate .net client and connected to the application, works just fine. But Postman even after connecting (shows connected successfully) receives no messages
Hello, first of all, great work. I was so stoked to see this added. I even tweeted about it:
Really stoked that @getpostman has finally brought native WebSocket Support. Tried it with our WebSocket Endpoint and the basic functionalities seems to be working fine. https://t.co/q8ZNRZCdQB
Have been using it extensively post that. I have a suggestion for one feature which I think can improve the user experience dramatically. So WebSocket Servers generally have an auto-disconnect when they sense inactivity. Generally, WebSocket libraries have configurable control frames which can be set - this means that these control frames count towards activity and keep the connection alive.
If this can be added to Postman, it will really enhance the WS Support. A keep-alive sort of a thing that sends the PING Control Frame as per-user configuration.
Is there a plan/possibility to add websocket requests as part of a collection flow? including tests and the ability to setEnvironment variable and continue to another request.
My use case:
I have a post request, after that I expect a websocket message from the server, and then I want to have another post/get request which its input is the content of the websocket message.
Sounds like a very common scenario.
I am very confused. The option to create a websocket request is not present on my screen. I am on Ubuntu but I don’t see any information on the learning page or the blog about the feature to imply I have any reason not to see it.
Ah, yes I am now looking at the changelog I’ve noticed the version number is much higher. In my defence it says the following for version number which I did check:
You’re on v7.36.5 . Snap will automatically update Postman whenever a new version is released.
Looks like Snap didn’t do what Postman said it was going to do . Genuinely thought it was a problem with this feature. Apologies for bringing up what was just a general issue.
Ever since the big update we got a few months back, every time i switch to the environments tab it sends me to my coffee break.
This is because once you have a bunch, it takes Postman around 10 minutes to load the environments list.
Happens to all my team on different workspaces.