Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message

Yii Http Laravel Package

yiisoft/yii-http

A lightweight HTTP layer for Yii, offering request/response handling, middleware support, and PSR standards integration. It provides clean abstractions for building structured, testable web endpoints that fit Yii's DI and configuration conventions.

View on GitHub
Deep Wiki
Context7

Yii HTTP Application

Frequently asked questions about Yii Http
Can I install yiisoft/yii-http in a Laravel application?
Technically possible via Composer, but not recommended. It is Yii3's HTTP application layer built around Yii's DI container, middleware dispatcher, and router, which overlap with Laravel's HTTP kernel. Embedding it creates competing request lifecycles and unclear ownership. Use it as a standalone Yii3 service behind an API boundary instead.
What is yiisoft/yii-http used for?
It provides a lightweight HTTP application layer for Yii3, including request/response handling, middleware dispatch, and PSR-7/PSR-15 integration. It fits Yii3 services that need structured, testable web endpoints using Yii's DI and configuration conventions. It is not a general-purpose Laravel HTTP replacement.
Does yiisoft/yii-http support Laravel 10 or Laravel 11?
No official Laravel support is provided. The package targets Yii3 conventions and is not designed around Laravel's kernel, container, routing, or Symfony HttpFoundation bridge. Any co-location would require a disposable compatibility spike and should not be assumed. The default assumption should be no direct Laravel compatibility.
How do I install yiisoft/yii-http?
Install it with Composer in a Yii3 project, typically as part of a Yii3 application skeleton or standalone PSR-15 service. You need to configure Yii's DI container, router, and middleware stack, and confirm PHP and PSR-7/PSR-15 implementation compatibility. It is not a drop-in Composer package for Laravel.
Is yiisoft/yii-http PSR-7 and PSR-15 compliant?
Yes, it integrates with PSR-7 HTTP messages and PSR-15 middleware conventions, which is central to its design. That makes it suitable for structured Yii3 HTTP services and middleware pipelines. However, PSR compliance alone does not make it compatible with Laravel's own request lifecycle.
What are alternatives to yiisoft/yii-http for Laravel developers?
For Laravel, use Laravel's HTTP kernel, routing, and middleware, or add PSR-15 middleware through an adapter if needed. For standalone PSR-15 services, consider Slim, Mezzio, or Laminas components. Choose yiisoft/yii-http only when you are intentionally building a Yii3 service.
Is yiisoft/yii-http safe for production use?
It is BSD-3-Clause licensed, which is commercially acceptable, but it has low community visibility and an unknown repository status in this assessment. Production use requires a named maintainer, pinned versions, CVE monitoring, and a security review. Treat repository visibility and long-term support as gating concerns before adoption.
How do I test a Yii3 HTTP application built with yiisoft/yii-http?
Test at the PSR-7/PSR-15 boundary by dispatching requests through the middleware stack and asserting responses. Use Yii's DI container to wire test doubles and keep handlers deterministic. Integration tests should cover routing, middleware order, and error handling in the chosen runtime.
What PHP versions and dependencies does yiisoft/yii-http require?
The assessment does not specify exact PHP or dependency versions, so validate Composer resolution against your project's PHP version and PSR-7/PSR-15 implementations. Check Yii3 dependencies for conflicts with Laravel's dependency tree before any spike. Pin versions and review the lock file in CI.
Should I use yiisoft/yii-http in a Laravel monolith or as a separate service?
Use it as a separate standalone Yii3 service only if Yii3 is justified for a new service. In a Laravel monolith it creates overlapping kernels and operational overhead, so it is a poor stack fit. Isolate it behind an API gateway or internal REST contract with OIDC/JWT, queues, and explicit data contracts.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core
nodisrupt/laravel-agent
sierratecnologia/media-manager