sipgo Define a maximum message size and avoid useless parsing

Define a maximum message size and avoid useless parsing

Open emiago opened this issue 1 year ago • 2 comments

TCP/UDP could be larger message size which may lead lot of bad parsing and therefore processing

Original comment suggestion https://github.com/emiago/sipgo/pull/36#issuecomment-1688888984

Aug 22 '23 21:08 emiago

TCP/WS now has default stream parsing.

Sep 07 '23 18:09 emiago

problem is multiple small messages that can still be in single flight. This still is good for security to define.

Oct 22 '23 15:10 emiago