On Monday, November 2, 2020 6:31:33 PM CET Florian Weimer wrote: > * Kamil Dudka: > > On Monday, November 2, 2020 5:57:29 PM CET Florian Weimer wrote: > >> * Kamil Dudka: > >> > As far as I know, (lib)curl has never silently transformed a protocol > >> > scheme explicitly specified with URL. This can be discussed upstream > >> > but I do not feel like starting the discussion myself. > >> > >> Curl does it for https://, so it should be fine for scp://. > > > > Could you please be more specific? What exactly does curl do for https:// > > ? > It automatically replaces the underlying HTTP transport with HTTP/2 if > the server replaces it. These protocols are about as similar as SCP and > SFTP, I would say. Thank you for clarifying it! The key difference is that the HTTP protocol upgrade to HTTP/2 (or HTTP/3 via Alt-Svc header) are covered by IETF specifications. There is also no protocol scheme to specify HTTP/2 explicitly in URL, unlike SCP vs. SFTP. Kamil > Thanks, > Florian _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
