Zend Diactoros Laravel Package

Getting Started

zend-diactoros is a PSR-7 implementation for HTTP messages (requests, responses, streams, etc.). Though archived and unmaintained, it’s still used in legacy Zend Framework/Laminas projects. Start by installing it via Composer:

composer require zendframework/zend-diactoros

Your first use case will likely be building or parsing HTTP messages—for example, constructing a response in a lightweight framework or middleware stack:

use Zend\Diactoros\Response;
use Zend\Diactoros\StatusCode;

$response = (new Response())
    ->withStatus(StatusCode::STATUS_OK)
    ->withHeader('Content-Type', 'text/plain')
    ->getBody()->write('Hello, PSR-7!');

Implementation Patterns

• Middleware Interoperability: Use ServerRequest and Response to integrate with PSR-15-style middleware (e.g., Expressive/Laminas Mezzio).
• Request Parsing: Instantiate ServerRequestFactory::fromGlobals() to convert $_SERVER, $_GET, $_POST, etc., into a typed ServerRequestInterface.
• Stream Management: Replace php://input manually with Zend\Diactoros\Stream for testability or in-memory streams:

  $stream = new Stream('php://temp', 'r+');
  $stream->write(json_encode(['status' => 'ok']));
  $response = new Response($stream, 200, ['Content-Type' => 'application/json']);
  

• Legacy Bridge: In older Laminas/Mezzio apps, ResponseInterface and ServerRequestInterface from this package feed directly into routing and dispatching layers.

Gotchas and Tips

• ⚠️ Archived & Deprecated: Use laminas/laminas-diactoros (the official fork) instead. The zendframework/ namespace is unmaintained and not compatible with modern PSR-7/17 extensions.
• Header & Body Mutability: Like all PSR-7 messages, objects are immutable—always assign the result of with*() methods:

  $response = $response->withHeader('X-Debug', 'true'); // OK
  $response->withHeader(...); // Broken: original untouched
  

• Stream Recycling Pitfall: Reusing a Stream instance across requests/responses can cause “stream already consumed” errors—always clone or create fresh streams in tests or pipelines.
• Extensibility: You can extend Response or ServerRequest to add domain-specific helpers (e.g., withJsonError()), but avoid overriding __toString()—PSR-7 messages aren’t meant to be rendered.
• Debugging Tip: Use var_dump($request->getUri()) or json_encode((array) $request) for quick inspection—but prefer unit tests over var_dump in production.