HTTP engine
triangle/engine-http provides Triangle\Http\App on Engine\App. The source onMessage path establishes connection/request context, checks the URI, considers static files and explicit routes, then resolves default controller routes/fallbacks. Middleware wraps callbacks before response sending; exceptions are handled by configured rendering, not silently granted authorization.
Requirements: PHP ^8.1, ext-curl, triangle/engine ^8, router ^2, middleware ^2. It conflicts with engine-ws. Web adds its own higher PHP/dependency constraints. Set config/server.php handler to the correct HTTP App through the scaffold rather than constructing incomplete application context manually.
The quick start exercises a JSON route. Web lifecycle, Router, Middleware and configuration describe its surrounding contracts. Test static-file restrictions, error paths and persistent request cleanup before production; the minimal route is not full engine acceptance.
Source reviewed 2026-10-17; Ivan Zorin / Localzet Group. Guide AGPL-3.0-or-later; package licenses retained.