Hi,
this is my second question here today, sorry if this is too much!
again, my version is 2.2.5, but we are considering upgrading, so please let me know also if is it possible to do the things I asked for in later versions.
I try to figure out the reason for my Websockets are closing within a couple of seconds from opening, then I realized I’m getting a different type of WebSockets in my service.
-while I’m using JMeter, there is an option to configure transport protocol, so I’m using “xhr-streaming” and my service is getting an object of WebSocket:
XhrStreamingSockJsSession[id=f78d06d6486747f88a96ef037a4a10a0]
The Uri:
http://127.0.0.1:9008/ws/notifications/744/f78d06d6486747f88a96ef037a4a10a0/xhr_streaming
also, the handshake headers has 5 keys & values:
{content-length=[0],
host=[127.0.0.1:9008],
connection=[Keep-Alive],
user-agent=[Apache-HttpClient/4.5.6 (Java/1.8.0_231)]
, accept-encoding=[gzip,deflate]}
While I am using Gatling, I couldn’t find a way to configure “xhr”, so my service is getting an object of WebSocket:
StandardWebSocketSession[id=189, uri=ws://127.0.0.1:9008/ws/notifications/websocket]
the handshake headers has 10 keys & values:
{accept=[application/json, text/plain, /],
cache-control=[no-cache], pragma=[no-cache],
accept-encoding=[gzip, deflate, sdch],
upgrade=[WebSocket],
connection=[Upgrade],
origin=[http://127.0.0.1:9008],
sec-websocket-key=[+54ozGAxVVNrl/UHSdFVzg==],
sec-websocket-version=[13], host=[127.0.0.1:9008]}
my questions are:
- there is an option to use “xhr-streaming” in Gatling? if so, how?
- I tried to configure the Jmeter handshake headers on my open Ws request in Gatling, but “connection” is overrides by Gatling from “keep alive” to “upgrade”, there is an option to control this?
Thanks and Happy Easter/Passover/Ramadan to you all
Maor