From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] http: make caching of redirect url optional
Date: Mon, 27 Dec 2021 14:08:02 -0500
Message-ID: <CAEEMt2=JkwQXQ8qg1fsL8pf2hzOSQ=s=+S_NJ6vaPKbU91+NrQ@mail.gmail.com> (raw)
In-Reply-To: <AS8PR04MB8913EF3EFFBA37CAD06C5212F5429@AS8PR04MB8913.eurprd04.prod.outlook.com>
Hi,
On Mon, Dec 27, 2021 at 4:38 AM Eran Kornblau <eran.kornblau@kaltura.com>
wrote:
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Ronald S. Bultje
> > Sent: Sunday, 26 December 2021 16:07
> > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] http: make caching of redirect url
> optional
> >
> > Hi,
> >
> > (I was asked to respond since I'm listed as HTTP maintainer, not sure I
> should be since I'm mostly working on video codecs nowadays.)
> >
> > On Tue, Nov 2, 2021 at 9:00 AM Eran Kornblau <eran.kornblau@kaltura.com>
> > wrote:
> >
> > > The motivation for this feature is S3 signatures – currently we have a
> > > problem where S3 signatures cannot be created with an expiration of
> > > more than 12H. In some cases, a transcoding task may execute for more
> > > than that.
> > > If we use a pre-signed S3 URL, and ffmpeg disconnects/seeks after the
> > > expiration of the URL, it will fail.
> > >
> > > The solution we are planning is to have some local server on the
> > > machine running ffmpeg that will generate an S3-signature, and
> > > redirect to the full pre-signed URL. For this to work, I need to
> > > disable the caching of redirects, and have ffmpeg always start from
> > > the initial URL.
> > > The nice thing about this solution is that the video data is pulled
> > > directly from S3 – in other words, the local server doesn’t hold any
> > > real load, it just builds the signature and returns a redirect.
> > >
> >
> > Uhm... This is a really weird solution, but it does look right.
> >
> > Generally speaking, we're typically concerned about the default being
> the right behaviour. I would say that (maybe after some time, at the next
> ABI break or so), 0 should be the default, not 1. This is the same as what
> Marton/Hendrik said also, I think, so consider this consensus. I would just
> do that with the appropriate ABI macros so the default behaviour changes at
> the next bump.
> >
> Thank you, Ronald!
>
> I attached a new patch with the change you requested, I hope I understood
> your intention correctly...
>
Yes, LGTM. I'll give it a few days to let Marton/Hendrik respond before I
push.
Ronald
_______________________________________________
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".
next prev parent reply other threads:[~2021-12-27 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AS8PR04MB8913E28EC1F461C48D366094F58B9@AS8PR04MB8913.eurprd04.prod.outlook.com>
[not found] ` <4a6752f0-c0fe-56d8-eb8b-a8413bc825c@passwd.hu>
[not found] ` <AM9PR04MB89223AD4495E1A64B935FF59F5919@AM9PR04MB8922.eurprd04.prod.outlook.com>
[not found] ` <AS8PR04MB8913DA5E11ADE490240E55AFF59B9@AS8PR04MB8913.eurprd04.prod.outlook.com>
[not found] ` <AS8PR04MB891345386E07FDCB6E3CB3F6F5629@AS8PR04MB8913.eurprd04.prod.outlook.com>
[not found] ` <AS8PR04MB891387CC3C1A66104A4F012BF5699@AS8PR04MB8913.eurprd04.prod.outlook.com>
[not found] ` <AS8PR04MB8913779EBFF54B9C4881A9A1F5709@AS8PR04MB8913.eurprd04.prod.outlook.com>
2021-12-16 11:02 ` Eran Kornblau
2021-12-26 14:06 ` Ronald S. Bultje
2021-12-27 9:38 ` Eran Kornblau
2021-12-27 19:08 ` Ronald S. Bultje [this message]
2021-12-31 19:46 ` Ronald S. Bultje
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='CAEEMt2=JkwQXQ8qg1fsL8pf2hzOSQ=s=+S_NJ6vaPKbU91+NrQ@mail.gmail.com' \
--to=rsbultje@gmail.com \
--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