Download the PHP package milpa/http-symfony without Composer

# Milpa HTTP Symfony > The **Symfony HttpFoundation adapter** for the Milpa PHP framework — the response value objects and the base controller a host's routing invokes. [](https://github.com/getmilpa/http-symfony/actions/workflows/ci.yml) [](https://packagist.org/packages/milpa/http-symfony) [](https://www.php.net/) [](LICENSE) `milpa/http` describes routes and handlers without committing to any HTTP implementation. This package is one implementation of the other half: what a controller *returns*, for a host that speaks Symfony's HttpFoundation. It is deliberately small. A host resolves a route to a controller method, calls it with an HttpFoundation `Request`, and gets back an `HttpResponse`. That is the whole contract. ## Install ## What lives here | Class | Responsibility | |-------|-----------------| | `HttpResponse` | The response a controller returns — a Symfony `Response` with the framework's own type, so a host can tell "a Milpa controller answered" from "something else did". | | `BlobResponse` | A binary/file response with the download headers already set. | | `BaseController` | What a controller extends: the container, plus the shorthands for the answers controllers actually give — `json()`, `cleanResponse()`, `redirect()`, `download()`. | ## Quick example The `#[Route]` attribute and `HttpMethod` in that example come from [`milpa/http`](https://packagist.org/packages/milpa/http), which this package does **not** require — see [Requirements](#requirements). A host that routes with it already has it; the controller base class and the responses below work the same without it. ## What is NOT here, and why **View rendering.** A responder that turns a template into a response needs a template engine, and that engine is not published yet. Shipping the class anyway would put code in your `vendor/` that cannot run — a package that can only fail is worse than one that is missing a feature. It lives host-side until the engine earns its own release. **PSR-7.** This is the HttpFoundation adapter. A host that speaks PSR-7 end to end does not need it: `milpa/runtime`'s kernel and `milpa/http`'s router are already PSR-7 native. ## Requirements - PHP **≥ 8.3** - [`symfony/http-foundation`](https://packagist.org/packages/symfony/http-foundation) **^7.4** - [`milpa/core`](https://packagist.org/packages/milpa/core) **>=0.6.2 <1.0** - [`psr/log`](https://packagist.org/packages/psr/log) **^3.0** **`milpa/http` is not one of them**, and that is the point of the split. This package is the other half of the sentence, not a layer on top of it: the router describes *where a request goes*, these classes are *what the controller hands back*, and no line here implements, extends or imports any contract of `milpa/http` — its interfaces (`RouterInterface`, `HandlerResolverInterface`, `MiddlewareResolverInterface`, `UrlGeneratorInterface`) are PSR-7/PSR-15 seams a host kernel fills, and it declares nothing at all about responses. A host that routes with `milpa/http` requires it directly; a host that routes some other way pays nothing for it here. ## Contributing Contributions are welcome — see [CONTRIBUTING.md](CONTRIBUTING.md). Please report security issues via [SECURITY.md](SECURITY.md), and note that this project follows a [Code of Conduct](CODE_OF_CONDUCT.md). ## License [Apache-2.0](LICENSE) © Rodrigo Vicente - TeamX Agency. --- Milpa is designed, built, and maintained by **[Rodrigo Vicente - TeamX Agency](https://teamx.agency/?utm_source=github&utm_medium=readme&utm_campaign=milpa&utm_content=http-symfony)**.