New in Symfony 3.4: Default request context for assets

Contributed by
Roland Franssen
in #21027.

Generating URLs in a command console is tricky because the console context doesn't know anything about HTTP requests, virtual hosts and domain names. This means that generating an absolute URL in a console command will always use http://localhost as the host name.

Symfony solves this problem with the router.request_context.* parameters, which define the hostname, HTTP scheme and base URL for console commands. When generating asset URLs with the asset() function in a command, the same problem occurs.

For example, if your application is installed in a subdirectory and have configured this parameter:

# app/config/parameters.yml
router.request_context.base_url: '/subfolder'

A call to asset('/foo/image.jpg') will result in /foo/image.jpg URL instead of the expected /subfolder/foo/image.jpg.

That's why in Symfony 3.4 we've introduced two new parameters called asset.request_context.base_path and to define the default request context for assets. In this same application, if you define this new parameter:

# app/config/parameters.yml
asset.request_context.base_path: '/subfolder'

Now, the asset('/foo/image.jpg') function will generate the expected /subfolder/foo/image.jpg URL.

Help the Symfony project!

As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.

New in Symfony 3.4: Default request context for assets

Tweet this


Note the subtle difference between router and assets:

router.request_context.base_url (URL style)
assets.request_context.base_path (path style)

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.