[FFmpeg-devel] [PATCH 09/10] lavf/file: handle standard file:// URLs.
Nicolas George
george at nsup.org
Sat Aug 14 11:17:53 EEST 2021
Marton Balint (12021-07-29):
> I meant the absolute path case from Appendix B:
>
> o The minimal representation of a local file with no authority field
> and an absolute path that begins with a slash "/". For example:
>
> * "file:/path/to/file"
It is precisely what I call semi-relative. Do you know of any software
that outputs this kind of URL?
I know software that produces file:/// URLs with percent encoding, so
FFmpeg needs to accept them. But file:/ with percent encoding, I do not,
and therefore we have freedom over them.
> Well, it will break compatiblity for cases like
> file://server/share/100%.txt because now percent encoding will be assumed...
>
> Maybe as the first step percent encoding should only be used for the 3-slash
> form, and the deprecation warning should be printed for the
> less-than-3-slash form. (People wanting percent encoding may use the 4-slash
> form which is also a thing...)
Indeed. Or we can make a smarted detection: check if there are percents
and they are followed by hex digits.
> And after 2 years of deprecation period the warning should be removed and
> percent encoded form can be used for all the cases.
>
> This way eventually the file: handling can be fully RFC compliant.
This is the ultimate goal, of course.
Regards,
--
Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20210814/19d71cfe/attachment.sig>
More information about the ffmpeg-devel
mailing list