Cannot open PDF's from the command line if the filepath is an URL

[Maarten5FEE]

I'm managing an application that uses the .NET command Process.Start to start Acrobat, and provides an  URL-string that links to a pdf file in Sharepoint as the only argument. The goal is to open this file in an editable state, where the user can save the file to this same URL-location when he's done. This command operates like the Windows command line interface, so it's pretty much the same as typing acrobat.exe "http://this/is/the/url" in a Windows prompt.

The problem we're facing is that this action fails with an "invalid path" error. While the file is both accessable and editable (it works fine if you open it in a webbrowser) Acrobat just cannot seem to open the file in this way. However, when you open Acrobat from the start menu and put the same URL in the File > Open... menu, it can open the file just fine and it can also be editted. So Acrobat does support opening and editting files from an URL...

It almost seems like the CLI-argument way does not operate the same as the File > Open... menu. Is there some argument I'm missing or is it simply not possible to open an URL with Acrobat from the CLI?

We're using Adobe Acrobat Pro DC | Continuous Release version 2021.001.20150

[Test Screen Name]

The command line hasn't been changed in 25 years. It expects a local path name. It can't be used to provide URLs or special paths for a plug-in.

[Maarten5FEE]

Is this not the case for Acrobat Reader DC? Because that program does seem to be able to open URL-paths from the CLI. It even asks if I want to "Check out & open", as if there's functionality built in to open and edit files from Sharepoint or another web-based DMS.