Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Timothy Allen <tim@treehouse.org.za>
Subject: Re: [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI, instead of stripping preceding characters.
Date: Wed, 21 May 2025 19:25:51 +0000
Message-ID: <DM8P223MB0365FEDBB738DA42DE02E21FBA9EA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <e9102839d8b84ae501e3481037449f5892280b35.camel@treehouse.org.za>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Timothy
> Allen via ffmpeg-devel
> Sent: Mittwoch, 21. Mai 2025 21:09
> To: ffmpeg-devel@ffmpeg.org
> Cc: Timothy Allen <tim@treehouse.org.za>
> Subject: Re: [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI,
> instead of stripping preceding characters.
> 
> On Wed, 2025-05-21 at 18:56 +0000, softworkz . wrote:
> > Why do you think it would require control over the server side?
> 
> The original ticket is referring to HLS, and specifically the manifest
> of HLS, which means a remotely-hosted M3U playlist.
> 
> In principle, the user could download the playlist, convert any
> relative URLs to absolute URLs, and percent-encode the URLs.
> 
> In practice, for most users, the URL will simply not play (or will skip
> any segments containing colons in the URL) without any indication of
> why the URL is failing.

What I mean and what the comment in the ticket is probably suggesting, 
is that the HLS demuxer should URL-encode the URL after combining the 
base url with the segment file name before making a request for the 
segment.

PS: Thanks for switching to plain-text.

Best,
sw


_______________________________________________
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".

  reply	other threads:[~2025-05-21 19:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 15:27 Timothy Allen via ffmpeg-devel
2025-05-20 19:49 ` Marton Balint
2025-05-20 20:03 ` softworkz .
2025-05-21  7:28   ` Timothy Allen via ffmpeg-devel
2025-05-21 18:56     ` softworkz .
2025-05-21 19:09       ` Timothy Allen via ffmpeg-devel
2025-05-21 19:25         ` softworkz . [this message]
2025-05-21 20:04           ` Timothy Allen via ffmpeg-devel
2025-05-21 19:14       ` [FFmpeg-devel] Posting correctly (was: Accept a colon in the path of a URI, instead of stripping preceding characters.) Nicolas George
  -- strict thread matches above, loose matches on Subject: below --
2025-05-20 15:27 [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI, instead of stripping preceding characters Timothy Allen via ffmpeg-devel

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=DM8P223MB0365FEDBB738DA42DE02E21FBA9EA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=tim@treehouse.org.za \
    /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