Weave Code
Http Laravel Package
vinelab/http
Vinelab HTTP is a lightweight Laravel HTTP client that simplifies sending GET, POST, PUT, PATCH, and DELETE requests, handling headers, query parameters, JSON payloads, authentication, and response parsing through a fluent, expressive API.
A smart, simple and fault-tolerant HTTP client for sending and receiving JSON and XML
Frequently asked questions about Http
- Is vinelab/http still maintained and does it support PHP 8 and Laravel 10 or 11?
- No. The last tagged release was on 2017-10-24 and there has been no upstream activity since, so it predates modern PHP and Laravel entirely. Its Composer constraints, transitive Guzzle and Illuminate dependencies, and missing PHP 8.x support make it a likely blocker on Laravel 9, 10, and 11. Greenfield adoption is not justified; treat it strictly as a legacy dependency in existing brownfield code.
- How do I install vinelab/http with Composer?
- It is installed with composer require vinelab/http, and on Laravel 5-era applications the service provider and facade may need to be registered in config/app.php. Because the package has not been updated since 2017, expect to adjust version constraints and possibly bypass PHP platform checks to get it resolving. Run composer why-not and a full dependency audit before committing to the install.
- What is vinelab/http actually used for?
- It is a lightweight HTTP client for sending and receiving JSON and XML, letting you issue GET, POST, PUT, PATCH, and DELETE requests through a fluent, expressive API. It handles headers, query parameters, JSON payloads, authentication, and response parsing. Typical usage is inside older Laravel monoliths that want a terse wrapper around outbound API calls.
- Does vinelab/http wrap Guzzle?
- The package pulls Guzzle in transitively through its Composer requirements, but the exact version it targets dates from the 2017 release and must be confirmed with a compatibility spike. Check which Guzzle major version resolves in your lock file, because that governs your TLS, redirect, and timeout defaults. Do not assume modern Guzzle 7 behavior based on the package documentation.
- How does vinelab/http handle errors, retries, and timeouts?
- The package markets itself as fault-tolerant, but retry counts, backoff strategy, timeout defaults, redirect limits, and exception mapping are not clearly documented and must be validated by reading the source or writing probe tests. Unbounded or aggressive retries can amplify load during an outage. Wrap call sites in an adapter so you can enforce explicit timeout and retry bounds and add circuit breaking, metrics, and consistent exception handling.
- Is vinelab/http safe for parsing XML responses?
- No security audit or CVE history is published for the package, and it has had no releases since 2017, so its XML handling around external entities and entity expansion is unverified. Test XXE and entity-expansion payloads in a sandbox before trusting it with untrusted XML. Prefer disabling external entity loading or migrating to a maintained client with an explicitly hardened XML parser.
- How do I migrate from vinelab/http to Laravel's Http facade?
- Inventory every usage first, then wrap the package behind your own HttpClientInterface so no domain code calls it directly. Freeze new usage, add contract tests around request and response mapping, and replace endpoint groups one at a time with Illuminate\Support\Facades\Http for Laravel 7 and later, or Guzzle or Symfony HttpClient elsewhere. Remove the package once the adapter has no remaining callers.
- Can I use vinelab/http outside of Laravel or with plain Guzzle?
- It is a convenience wrapper built for Laravel-era PHP code and pulls in Illuminate dependencies, so it is not a clean fit for framework-agnostic services. For non-Laravel projects use Guzzle, Symfony HttpClient, or a PSR-18 client with PSR-7 messages directly. If you must keep it, contain it in a separate legacy service instead of spreading it into new code.
- How do I test code that uses vinelab/http?
- The package has no verified, current test coverage, so build your own contract tests asserting request construction, header and query handling, JSON and XML decoding, and error mapping. Introduce an internal adapter interface with a fake implementation so unit tests never hit the network, and keep a small set of integration tests against a stub server for the real client path. This also makes the eventual switch to Laravel's Http client mechanical rather than risky.
- What are the alternatives to vinelab/http?
- For Laravel 7 and later use the built-in Illuminate\Support\Facades\Http client, which is maintained and supports retries, timeouts, and testing fakes out of the box. For framework-agnostic PHP use Guzzle, Symfony HttpClient, or any PSR-18 client with PSR-7 messages. All of these have active maintenance, published security processes, and current PHP 8 support.
Weaver
How can I help you explore Laravel packages today?