[FFmpeg-devel] [PATCH]libavformat/http: fix http error eof
michael at niedermayer.cc
Fri Jun 2 00:55:28 EEST 2017
On Thu, Jun 01, 2017 at 07:48:38AM -0400, Ronald S. Bultje wrote:
> On Thu, Jun 1, 2017 at 2:27 AM, raymond zheng <raymondzheng1412 at gmail.com>
> > This patch is only for solving the bug introduced by chunksize has been
> > initial set as UINT64 MAX.
> I understand. So what will happen if the server responds that the chunksize
> is really actually UINT64_MAX? How do we distinguish between that and
> chunksize being unset (which is what UINT64_MAX currently means)? We'll
> need a flag to indicate whether chunksize is specified by the server or
> not, right?
does UINT64_MAX chunksize make sense ?
doesnt this indicate that theres a really huge chunk ?
or does it have some special meaning ?
iam asking because this feels a bit odd. Could a server use
UINT64_MAX + 1 instead of UINT64_MAX ? If so the point of failure moves
by one in UINT64_MAX by adding a flag, or maybe i misunderstand
ive briefly looked at rfc7230 but cant really find any limit on chunksize
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Republics decline into democracies and democracies degenerate into
despotisms. -- Aristotle
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 181 bytes
Desc: Digital signature
More information about the ffmpeg-devel