- Is ottsch/http-adapter-bundle a Laravel package?
- No. It is a Symfony bundle (WidopHttpAdapterBundle) that registers an HTTP adapter service through Symfony's bundle, kernel, and dependency injection conventions, and Laravel does not consume Symfony bundles. For a Laravel application the equivalent capability comes from Illuminate\Support\Facades\Http or Guzzle directly. Treat this package as a legacy Symfony 2/3 artifact, not a Laravel dependency.
- How do I install and register WidopHttpAdapterBundle?
- You install it with composer require ottsch/http-adapter-bundle and then register the bundle in AppKernel for a Symfony 2.x or 3.x application, followed by configuring an adapter in your config. There is no Laravel service provider and no Symfony Flex recipe, so nothing is auto-discovered. In a Symfony 4+ application you would have to write the kernel registration and DI wiring yourself.
- Which Symfony and PHP versions does this bundle support?
- The bundle targets the Symfony 2.x/3.x era; its last release was January 2019, which predates Symfony 4 autowiring conventions and the current symfony/http-client component. Its transitive dependencies (Symfony components, Guzzle/Buzz/Zend adapters, PSR versions) are almost certainly end-of-life and may block PHP 8.x runtimes. Verify the full dependency tree resolves before assuming it installs on a modern stack.
- Is this package maintained and safe to use in production?
- It has zero stars, zero dependents, and no release since January 2019, and the repository is a fork of the original Widop bundle with no visible maintainer. There is no issue triage and no security response path. A team adopting it should treat it as vendored code they now own rather than a supported dependency.
- What is the Laravel alternative to this bundle?
- Laravel ships Illuminate\Support\Facades\Http, a Guzzle wrapper with retries, timeouts, fakes, and testing assertions built in. Standalone Guzzle 7 covers anything outside Laravel, and Symfony applications should use symfony/http-client. Adopting this bundle buys nothing the platform does not already provide better.
- Can I use this bundle in Laravel with a service provider shim?
- You could write a Laravel service provider or DI alias to expose the underlying adapter, but at that point you are maintaining a private fork of an abandoned wrapper. The bundle's only real value was adapter swapping, and modern stacks standardize on PSR-18 and Guzzle, so the abstraction is obsolete. For a greenfield Laravel project the answer is almost certainly no.
- What adapters does WidopHttpAdapterBundle support?
- It exposes the Widop\HttpAdapter interface with implementations for cURL, Buzz, Zend, and Guzzle behind a single configurable service. The point was to let you swap HTTP transports without changing call sites. That abstraction is now redundant because PSR-18 and Guzzle 7 have become the standard interchange.
- How do I migrate off this bundle?
- Start by grepping for the widop_http_adapter service ID, the bundle class, and direct Widop\HttpAdapter interface usage, then classify each call site by feature need such as simple GET/POST, retries, auth, streaming, and timeouts. Capture the current timeouts, retry counts, SSL settings, and error handling for each call site, because those are what silently change during a swap. Build a thin internal client wrapping Illuminate\Support\Facades\Http or Guzzle that preserves existing method signatures, run the old and new paths in parallel, and use Http::fake() for test coverage before removing the bundle.
- Does it work on PHP 8 and modern dependency trees?
- Probably not without work. The bundle was last released in January 2019 and its dependency chain includes EOL Symfony components and PSR versions that may not resolve on PHP 8.x. Run a composer update in a scratch project to confirm before committing to any migration plan, and expect to pin or patch transitive dependencies.
- How do I test code that depends on this bundle?
- The bundle's testing seam is its mock adapter, which lets you substitute a fake implementation of Widop\HttpAdapter in the container. If you migrate to Laravel, replace those assertions with Http::fake() and the built-in request assertion helpers, or use Guzzle's MockHandler for standalone code. Inventory the tests that touch the mock adapter early, since they are the part of the migration most likely to be underestimated.