Re: [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI, instead of stripping preceding characters. - Timothy Allen via ffmpeg-devel

From: Timothy Allen via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: "softworkz ." <softworkz@hotmail.com>,
	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 09:28:54 +0200
Message-ID: <ae8448e9dad2b960ad2d6d991afb714c5cffd369.camel@treehouse.org.za> (raw)
In-Reply-To: <DM8P223MB0365F686E1B0DF06096E60A4BA9FA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On Tue, 2025-05-20 at 20:03 +0000, softworkz . wrote:
> I was just about to reply and suggest to replace those colons with
> %3A
> (url-encoded) when I read the ticket, which already suggests that.
> 
> Have you tried it? It sounds like a much better way to me.

I think this would be a common-sense solution as long as one controls
the server/content.

The reason I submitted the patch anyway was because not everyone will
control the content they're consuming, and because, although I
acknowledge it technically breaks RFCs, there is an argument that the
RFC's behaviour is surprising; we can certainly see that other
applications (Safari, in the linked ticket) break the RFC as well.

I can certainly understand if the patch is rejected -- even if it
didn't break the RFC, Postel's Law is not in vogue any longer. However,
I think the workflows that it might break ("host:port", with no scheme
or path) are much less obvious and intuitive than the workflows that it
rescues.

Regardless of the decision, thanks for reviewing the patch!

Best,

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