HTTP Handler Middleware

Since heptacom/heptaconnect-portal-base: 0.9.2

A portal can respond to an HTTP request using HTTP Handlers. To provide features for multiple HTTP handlers, you can use these middlewares.


With more and more implementations of HTTP handlers, shared code will occur e.g. authentication check, logging and profiling. To share this code you can either copy code snippets or use extracted services over and over again. With HTTP middlewares known from PSR-15 you can also write code that intercept every inbound HTTP request for your HTTP handlers.


Services of type \Psr\Http\Server\MiddlewareInterface will automatically get the service tag heptaconnect.http.handler.middleware. All services with the tag heptaconnect.http.handler.middleware will be executed before an HTTP Handler will receive the request. Adding a single file to your code will be sufficient for reoccurring tasks of your HTTP handlers like the following example for profiling:

use Heptacom\HeptaConnect\Portal\Base\Profiling\ProfilerContract;
use Psr\Http\Message\ResponseInterface;
use Psr\Http\Message\ServerRequestInterface;
use Psr\Http\Server\MiddlewareInterface;
use Psr\Http\Server\RequestHandlerInterface;

final class ProfilerMiddleware implements MiddlewareInterface
    private ProfilerContract $profiler;

    private bool $profilingEnabled;

    public function __construct(ProfilerContract $profiler, bool $configProfilingEnabled)
        $this->profiler = $profiler;
        $this->profilingEnabled = $configProfilingEnabled;

    public function process(ServerRequestInterface $request, RequestHandlerInterface $handler): ResponseInterface
        if (!$this->profilingEnabled) {
            return $handler->handle($request);

        $this->profiler->start(\sprintf('http handler %s %s', $request->getMethod(), $request->getUri()));

        try {
            $response = $handler->handle($request);
        } catch (\Throwable $exception) {

            throw $exception;


        return $response;