I've dug through the source code of go.net/websocket and I see no way to
specify an limit to an websocket.Message.Receive call, in my own tests I've
found that this code tries to receive an message no matter how large it may
be, in my tests I was only able to try messages of about 50MB, I would
imagine though that there is no hard limit set anywhere, this means any
websocket server could be attacked and taken down by only one single client
sending large amounts of fake data... at least this is what I think, I
would love to be proven wrong about this.
I would like to be able to specify an Message size limit (frame size limit?
I am unsure what the proper term would be), that way single websocket
connection could send an massive message, thus using up all my memory and
crashing the server program.
I've googled around an bit, and found this link regarding maximum header
it he says that he was testing close to the same thing as me -- though it
seems the original topic was never discussed in depth.
I've also checked the issue tracker and found nothing related to this..
Is it possible to do this? Is it considered an bug?
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.