With Postman v8 you can test Websockets - great! But..
When testing STOMP servers you will encounter a problem:
The body is then followed by the NULL octet.
See https://stomp.github.io/stomp-specification-1.2.html#STOMP_Frames
The only way (on windows) to get the NULL octet into the frame is by using the "binary/Base64" encoding (see screenshot below).
To easily convert the frame you can use Notepad++:
- Activate "Character Panel"
- Add "NULL" at the end of the frame (after all headers and body) - make sure to actually click on "NULL"
- Select complete frame and encode it to Base64
If you found an easier way, please comment!
Top comments (7)
Hi, thank you for your tips.
Inspired by your effort I found a way of adding the NULL char at the end:
It's not beautiful, but less hassle than going through base64 encoding
Setting environment variable didn't work for me. I used global variables
pm.globals.set("NULL_CHAR", '\0');
For linux, setting
NULL_CHAR
as^@
worked for me.pm.globals.set("NULL_CHAR",'^@')
Nice!
So how to use
pm.globals.set("NULL_CHAR", '\0');
with Websockets ? Somebody succeded it ?
if you want something easier and user friendly, use apic to test your websocket with stomp. just a chrome extention, it works out of the box: docs.apic.app/tester/test-websocket
Mr. Schreiber, I don't use the word "hero" lightly, but you are the greatest hero in American history. (Thank you for saving me hours of beating my head against the wall.)