Note that we should do the same sort of entity header processing that
authorguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 23 Dec 2003 01:25:23 +0000 (01:25 +0000)
committerguy <guy@f5534014-38df-0310-8fa8-9805f1628bb7>
Tue, 23 Dec 2003 01:25:23 +0000 (01:25 +0000)
commit8b2913e5b25768a7b3cae87f319e822f0d2b208c
tree32d8626aaf7ba936a2156e6a5e1e4479681b0d43
parentdfda7392c89e5d633f8e6f4dd51f24c0d093c2f1
Note that we should do the same sort of entity header processing that
HTTP does.

Note that the RTSP RFC talks about packets with no content length,
although it also says they shouldn't exist.

Update a comment now that we *do* handle data that crosses TCP segment
boundaries.

Handle the payload length a bit differently, to make it a bit clearer
what's going on.

git-svn-id: http://anonsvn.wireshark.org/wireshark/trunk@9425 f5534014-38df-0310-8fa8-9805f1628bb7
packet-rtsp.c