Change/Remove ClientWebSocket ping packet body

[zxcvqwerasdf]

As i know, there is no way send ping's with ClientWebSocket directly, only by using

_webSocket.Options.KeepAliveInterval

But it's sends integer in body

Can you add feature to do not send ping packet body? Only ping opcode?
Thank you.

[MihaZupan]

Why do you care whether the extra bytes are sent / what's the motivation to avoid it?

[zxcvqwerasdf]

Why do you care whether the extra bytes are sent / what's the motivation to avoid it?

I am using custom ping/pong on the server and i need custom data in ping message

[CarnaViire]

custom ping/pong on the server

// TL;DR: Custom Ping/Pong on the server could only apply to server's Pings, it is fully independent from what the client sends in the client's Pings.

@zxcvqwerasdf
Ping/Pongs initiated from the client side and from the server side are two separate things.

By RFC, the receiver of a Ping frame MUST echo back the data in the Pong response:

   A Pong frame sent in response to a Ping frame must have identical
   "Application data" as found in the message body of the Ping frame
   being replied to.

What that means:

1. If Ping/Pongs are initiated from the client side:

   • the server must echo the data back, and there could be nothing custom about it. Imagine your server will also have another client that is not on .NET -- this client would be free to send whatever (fitting the RFC requirements), and the server must comply.

2. If Ping/Pongs are initiated from the server side:

   • it only matters what ClientWebSocket responds in the Pong frame. And it will, as well, echo back whatever custom data the server sent in the server's Ping.

[dotnet-policy-service]

This issue has been marked needs-author-action and may be missing some important information.

[MihaZupan]

custom data in ping message

What sort of information would you want to transmit?
What's the motivation behind using pings instead of regular messages? Note that the size of ping data is very limited whereas regular messages can be arbitrarily large.

[dotnet-policy-service]

This issue has been automatically marked no-recent-activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no-recent-activity.

[dotnet-policy-service]

This issue will now be closed since it had been marked no-recent-activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the issue, but please note that the issue will be locked if it remains inactive for another 30 days.