Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Marton Balint <cus@passwd.hu>
To: Timothy Allen via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI, instead of stripping preceding characters.
Date: Tue, 20 May 2025 21:49:40 +0200 (CEST)
Message-ID: <adace928-a2c3-7208-c402-ad6cb67888cb@passwd.hu> (raw)
In-Reply-To: <aCyfe0AsMAD1lfSw@treehouse.org.za>



On Tue, 20 May 2025, Timothy Allen via ffmpeg-devel wrote:

> Good day
>
> I wanted to offer a discussion of the referenced patch.
>
> I have found that, when a link in an extended M3U file (as used by HLS)
> includes a colon, FFmpeg will fail to load the file.
>
> The bug has already been reported: https://trac.ffmpeg.org/ticket/10679
>
> The error reads:
> [hls @ 0x78dea4000c80] Failed to open segment 0 of playlist 0 [hls @
> 0x78dea4000c80] Segment 0 of playlist 0 failed too many times, skipping
>
> The referenced patch fixes the issue. However, it is worth noting that
> the patch changes the behavior of one of the unit tests:
>
> - http://a/b/c/d;p?q g:h                  => g:h
> + http://a:b/c/d;p?q e                    => http://a:b/c/e
>
> The original unit test derives from the following two trac tickets:
> https://trac.ffmpeg.org/ticket/8813
> https://trac.ffmpeg.org/ticket/8814
>
> This is a breaking change, and, in particular, violates one specific
> example given in the rfc at
> https://tools.ietf.org/html/rfc3986#section-5.4 (the first example). In
> particular, it will affect cases where a URL consists only of
> host:port, with no scheme or path, and the base URL links to an
> unrelated host. Where before, the new link would take the form of
> "host:port", the new link will now use "host:port" as the last element
> of the path.
>
> I believe that this behaviour is more intuitive given modern use of
> URIs (and is replicated in many browsers), but I recognise this is a
> matter of taste.

Sorry, but I'd rather not break RFC compliant parsing because of 
problematic files. Feel free however to add some more context to the 
ticket, like which browsers and/or media players support such a file, 
which don't. And how the ones which do support it distinguish between an 
URL scheme and a relative URL with a colon in the first path component, 
e.g.

video:first.ts or http:first.ts

Thanks,
Marton
_______________________________________________
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-20 19:53 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 [this message]
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 .
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=adace928-a2c3-7208-c402-ad6cb67888cb@passwd.hu \
    --to=cus@passwd.hu \
    --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