From: Timothy Allen <t...@treehouse.org.za> Sent: Mittwoch, 21. Mai 2025 09:29 To: softworkz . <softwo...@hotmail.com>; FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] Accept a colon in the path of a URI, instead of stripping preceding characters.
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. Why do you think it would require control over the server side? Almost every http server in the world will decode the URL as one of its first steps. When you have a file on disk with a space in it like “/httproot/my file.html” then a URL like “http://server/my%20file.html” will retrieve that file without any change to the http server. 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-requ...@ffmpeg.org with subject "unsubscribe".
