symfony
diff --git a/‎components/asset.rst
Lines changed: 4 additions & 2 deletions b/‎components/asset.rst
Lines changed: 4 additions & 2 deletions
diff --git a/‎reference/configuration/framework.rst
Lines changed: 16 additions & 4 deletions b/‎reference/configuration/framework.rst
Lines changed: 16 additions & 4 deletions
@@ -166,8 +166,7 @@ In those cases, use the
     // result: build/css/app.b916426ea1d10021f3f17ce8031f93c2.css
 
 If your JSON file is not on your local filesystem but is accessible over HTTP,
-you can use the ...
-:class:`Symfony\\Component\\Asset\\VersionStrategy\\RemoteJsonManifestVersionStrategy`
+use the :class:`Symfony\\Component\\Asset\\VersionStrategy\\RemoteJsonManifestVersionStrategy`
 with the :doc:`HttpClient component </components/http_client>`::
 
     use Symfony\Component\Asset\Package;
@@ -178,6 +177,9 @@ with the :doc:`HttpClient component </components/http_client>`::
     $manifestUrl = 'https://cdn.example.com/rev-manifest.json';
     $package = new Package(new RemoteJsonManifestVersionStrategy($manifestUrl, $httpClient));
 
+.. versionadded:: 5.1
+
+    The ``RemoteJsonManifestVersionStrategy`` was introduced in Symfony 5.1.
 
 Custom Version Strategies
 .........................
 
@@ -1927,10 +1927,11 @@ json_manifest_path
 
 **type**: ``string`` **default**: ``null``
 
-The file path to a ``manifest.json`` file containing an associative array of asset
-names and their respective compiled names. A common cache-busting technique using
-a "manifest" file works by writing out assets with a "hash" appended to their
-file names (e.g. ``main.ae433f1cb.css``) during a front-end compilation routine.
+The file path or absolute URL to a ``manifest.json`` file containing an
+associative array of asset names and their respective compiled names. A common
+cache-busting technique using a "manifest" file works by writing out assets with
+a "hash" appended to their file names (e.g. ``main.ae433f1cb.css``) during a
+front-end compilation routine.
 
 .. tip::
 
@@ -1951,6 +1952,8 @@ package:
             assets:
                 # this manifest is applied to every asset (including packages)
                 json_manifest_path: "%kernel.project_dir%/public/build/manifest.json"
+                # you can use absolute URLs too and Symfony will download them automatically
+                # json_manifest_path: 'https://cdn.example.com/manifest.json'
                 packages:
                     foo_package:
                         # this package uses its own manifest (the default file is ignored)
@@ -1972,6 +1975,8 @@ package:
             <framework:config>
                 <!-- this manifest is applied to every asset (including packages) -->
                 <framework:assets json-manifest-path="%kernel.project_dir%/public/build/manifest.json">
+                <!-- you can use absolute URLs too and Symfony will download them automatically -->
+                <!-- <framework:assets json-manifest-path="https://cdn.example.com/manifest.json"> -->
                     <!-- this package uses its own manifest (the default file is ignored) -->
                     <framework:package
                         name="foo_package"
@@ -1991,6 +1996,8 @@ package:
             'assets' => [
                 // this manifest is applied to every asset (including packages)
                 'json_manifest_path' => '%kernel.project_dir%/public/build/manifest.json',
+                // you can use absolute URLs too and Symfony will download them automatically
+                // 'json_manifest_path' => 'https://cdn.example.com/manifest.json',
                 'packages' => [
                     'foo_package' => [
                         // this package uses its own manifest (the default file is ignored)
@@ -2004,6 +2011,11 @@ package:
             ],
         ]);
 
+.. versionadded:: 5.1
+
+    The option to use an absolute URL in  ``json_manifest_path`` was introduced
+    in Symfony 5.1.
+
 .. note::
 
     This parameter cannot be set at the same time as ``version`` or ``version_strategy``.