Caution
The documentation you are viewing is for an older version of this component.
Switch to the latest (v3) version.
Helpers
In This Article
ServerUrlHelper
Zend\Expressive\Helper\ServerUrlHelper provides the ability to generate a full
URI by passing only the path to the helper; it will then use that path with the
current Psr\Http\Message\UriInterface instance provided to it in order to
generate a fully qualified URI.
Usage
When you have an instance, use either its generate() method, or call the
instance as an invokable:
// Using the generate() method:
$url = $helper->generate('/foo');
// is equivalent to invocation:
$url = $helper('/foo');
The helper is particularly useful when used in conjunction with the UrlHelper, as you can then create fully qualified URIs for use with headers, API hypermedia links, etc.:
$url = $serverUrl($url('resource', ['id' => 'sha1']));
The signature for the ServerUrlHelper generate() and __invoke() methods is:
function ($path = null) : string
Where:
$path, when provided, can be a string path to use to generate a URI.
Creating an instance
In order to use the helper, you will need to inject it with the current
UriInterface from the request instance. To automate this, we provide
Zend\Expressive\Helper\ServerUrlMiddleware, which composes a ServerUrl
instance, and, when invoked, injects it with the URI instance.
As such, you will need to:
- Register the
ServerUrlHelperas a service in your container. - Register the
ServerUrlMiddlewareas a service in your container. - Register the
ServerUrlMiddlewareas pipeline middleware, anytime before the routing middleware.
The following examples demonstrate registering the services.
use Zend\Expressive\Helper\ServerUrlHelper;
use Zend\Expressive\Helper\ServerUrlMiddleware;
use Zend\Expressive\Helper\ServerUrlMiddlewareFactory;
// zend-servicemanager:
$services->setInvokableClass(ServerUrlHelper::class, ServerUrlHelper::class);
$services->setFactory(ServerUrlMiddleware::class, ServerUrlMiddlewareFactory::class);
// Pimple:
$pimple[ServerUrlHelper::class] = function ($container) {
return new ServerUrlHelper();
};
$pimple[ServerUrlMiddleware::class] = function ($container) {
$factory = new ServerUrlMiddlewareFactory();
return $factory($container);
};
// Aura.Di:
$container->set(ServerUrlHelper::class, $container->lazyNew(ServerUrlHelper::class));
$container->set(ServerUrlMiddlewareFactory::class, $container->lazyNew(ServerUrlMiddlewareFactory::class));
$container->set(
ServerUrlMiddleware::class,
$container->lazyGetCall(ServerUrlMiddlewareFactory::class, '__invoke', $container)
);
To register the ServerUrlMiddleware as pipeline middleware anytime before the
routing middleware:
use Zend\Expressive\Helper\ServerUrlMiddleware;
// Programmatically:
$app->pipe(ServerUrlMiddleware::class);
$app->pipeRoutingMiddleware();
$app->pipeDispatchMiddleware();
// Or use configuration:
// [
// 'middleware_pipeline' => [
// ['middleware' => ServerUrlMiddleware::class, 'priority' => PHP_INT_MAX],
// /* ... */
// ],
// ]
The following dependency configuration will work for all three when using the Expressive skeleton:
return [
'dependencies' => [
'invokables' => [
ServerUrlHelper::class => ServerUrlHelper::class,
],
'factories' => [
ServerUrlMiddleware::class => ServerUrlMiddlewareFactory::class,
],
],
'middleware_pipeline' => [
['middleware' => ServerUrlMiddleware::class, 'priority' => PHP_INT_MAX],
/* ... */
],
];
Skeleton configures helpers
If you started your project using the Expressive skeleton package, the
ServerUrlHelperandServerUrlMiddlewarefactories are already registered for you, as is theServerUrlMiddlewarepipeline middleware.
Using the helper in middleware
Compose the helper in your middleware (or elsewhere), and then use it to generate URI paths:
use Zend\Expressive\Helper\ServerUrlHelper;
class FooMiddleware
{
private $helper;
public function __construct(ServerUrlHelper $helper)
{
$this->helper = $helper;
}
public function __invoke($request, $response, callable $next)
{
$response = $response->withHeader(
'Link',
$this->helper->generate() . '; rel="self"'
);
return $next($request, $response);
}
}
Found a mistake or want to contribute to the documentation? Edit this page on GitHub!