Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP: Cannot check status code on ws.close #4116

Open
domi-nika60 opened this issue Jul 26, 2021 · 2 comments
Open

HTTP: Cannot check status code on ws.close #4116

domi-nika60 opened this issue Jul 26, 2021 · 2 comments

Comments

@domi-nika60
Copy link

Hi,

I would like to test (check) status code of WebSocket close actions. Is there any way to do it?
I did not find neither any documentation about this nor examples in google.
In my project I would like to accept 1000 status code as well as 1013.
Could you help me with this and provide any examples of such implementation?

I'm using example ws-code configured like:

.exec(
  ws("WS Connect")
    .connect(some_path)
    .header(...)
.pause(1)
.exec(
  ws("Send some data")
    .sendText(...)
)
.pause(1)
.exec(ws("WS Close").close)

I have no idea how to implement check function or anything which will be working to check status codes of my ws.close execution. Is it not supported?

@slandelle
Copy link
Member

We're not currently checking the code of close frames. A close frame would trigger an error if it's received while there's an ongoing action: sending an outbound message or waiting for an inbound message.
IMHO, receiving a close frame during those step with a 1013 code should still be considered an error: your system is not able to withstand the load.

@slandelle slandelle changed the title Cannot check status code on ws.close HTTP: Cannot check status code on ws.close Aug 5, 2021
@domi-nika60
Copy link
Author

Hello,
any updates about this issue? Is there any other possibility to run ws.close?

@gatling gatling deleted a comment from rjaros87 Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants