Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Aman Karmani <ffmpeg@tmm1.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] http: Improve handling of Content-Range with Transfer-Encoding:chunked
Date: Wed, 2 Feb 2022 17:26:52 -0800
Message-ID: <CAK=uwuz6tAi2WdAWcCoWAO+fX5ACak-xF=OW_+EW6sfyYbPEzg@mail.gmail.com> (raw)
In-Reply-To: <20220202234953.6337-1-vittorio.giovara@gmail.com>

On Wed, Feb 2, 2022 at 3:50 PM Vittorio Giovara <vittorio.giovara@gmail.com>
wrote:

> From: Justin Ruggles <justin.ruggles@gmail.com>
>
> When Transfer-Encoding:chunked is used, the client must ignore a
> Content-Length header, if present. However, it should not ignore a
> Content-Range header, which also includes the full size of the
> entity.
> ---
>  libavformat/http.c | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/libavformat/http.c b/libavformat/http.c
> index 8f39d11a88..c89f8a5517 100644
> --- a/libavformat/http.c
> +++ b/libavformat/http.c
> @@ -132,6 +132,7 @@ typedef struct HTTPContext {
>      int64_t expires;
>      char *new_location;
>      AVDictionary *redirect_cache;
> +    uint64_t filesize_from_content_range;
>  } HTTPContext;
>
>  #define OFFSET(x) offsetof(HTTPContext, x)
> @@ -839,7 +840,7 @@ static void parse_content_range(URLContext *h, const
> char *p)
>          p     += 6;
>          s->off = strtoull(p, NULL, 10);
>          if ((slash = strchr(p, '/')) && strlen(slash) > 0)
> -            s->filesize = strtoull(slash + 1, NULL, 10);
> +            s->filesize_from_content_range = strtoull(slash + 1, NULL,
> 10);
>

The size part of the range header is optional, and can be '*' as well.

See also
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20211005233244.37582-1-ffmpeg@tmm1.net/


>      }
>      if (s->seekable == -1 && (!s->is_akamai || s->filesize != 2147483647))
>          h->is_streamed = 0; /* we _can_ in fact seek */
> @@ -1341,6 +1342,7 @@ static int http_read_header(URLContext *h)
>      av_freep(&s->new_location);
>      s->expires = 0;
>      s->chunksize = UINT64_MAX;
> +    s->filesize_from_content_range = UINT64_MAX;
>
>      for (;;) {
>          if ((err = http_get_line(s, line, sizeof(line))) < 0)
> @@ -1356,6 +1358,10 @@ static int http_read_header(URLContext *h)
>          s->line_count++;
>      }
>
> +    // filesize from Content-Range can always be used, even if using
> chunked Transfer-Encoding
> +    if (s->filesize_from_content_range != UINT64_MAX)
> +        s->filesize = s->filesize_from_content_range;
> +
>      if (s->seekable == -1 && s->is_mediagateway && s->filesize ==
> 2000000000)
>          h->is_streamed = 1; /* we can in fact _not_ seek */
>
> --
> 2.34.1
>
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  parent reply	other threads:[~2022-02-03  1:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 23:49 Vittorio Giovara
2022-02-02 23:49 ` [FFmpeg-devel] [PATCH 2/2] http: Send a Range header even when the offset is 0 Vittorio Giovara
2022-02-03  1:26 ` Aman Karmani [this message]
2022-02-03 14:12   ` [FFmpeg-devel] [PATCH 1/2] http: Improve handling of Content-Range with Transfer-Encoding:chunked Derek Buitenhuis
2022-02-09  0:55     ` Vittorio Giovara
2022-02-09  8:49       ` Paul B Mahol
2022-02-11 12:02         ` Vittorio Giovara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK=uwuz6tAi2WdAWcCoWAO+fX5ACak-xF=OW_+EW6sfyYbPEzg@mail.gmail.com' \
    --to=ffmpeg@tmm1.net \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git