Hi,
I’m using 3.3.1 and I’m unable to get a response from simulation connecting to WebSocket on azure signal r. Trying to debug the issue, and connect to my localhost I get IllegalArgumentException when doing the POST request that will return connectionId for the WebSocket connection. The Post request and exception is as follow:
Can you reproduce with 3.4.1?
Hi,
Thank you for the fast response.
With 3.4.1 request times out:
“api_negotiate_post: KO i.g.h.c.i.RequestTimeoutException: Request timeout to localhost/127.0.0.1:44386 after 60000 ms”
My issue starts with the fact that I’m unable to get a response/inboundMessage/checkWorking for websocket simulation, I tried running the original simulation against 3.4.1 (maybe checks would work in this version) and the socket crashes with " Invalid handshake response getStatus: 503 Service Temporarily Unavailable" (it works with 3.3.1).
What should i do?
A terça-feira, 3 de novembro de 2020 à(s) 16:38:29 UTC, Stéphane Landelle escreveu:
What should i do?
As explained in the group’s terms:
- Provide a Short, Self Contained, Correct (Compilable), Example (see http://sscce.org/)
Your problem is that you shouldn’t add the Upgrade header, that’s messing up with the request.
There are several HTTP headers you’d better let Gatling handle for you: Upgrade, Host, Content-Length, Referrer.