When creating/updating an asset via the Content Management API it is now possible to provide an URI in the file's upload property that points to a resource exclusively served via HTTP/2.

During asset processing the file is fetched with HTTP/2 support and falls back to HTTP/1.1 if necessary.

This does not affect URIs served via HTTP/1.1 and they proceed to work as before.