A Symfony bundle that integrates Guzzle HTTP client with debugging tools, configuration, and middleware.
CsaGuzzleBundle is a Symfony bundle that integrates the Guzzle HTTP client (versions 4.0 and above) into Symfony applications. It provides deep integration with Symfony's debugging tools like the web debug toolbar and profiler, and simplifies client configuration through YAML files. This makes managing and monitoring HTTP requests more seamless within Symfony projects.
Symfony developers who need to make HTTP requests from their applications and want native integration with Symfony's debugging and configuration systems. It is particularly useful for those using Guzzle 6 or later in Symfony 2.8+ environments.
Developers choose this bundle over plain Guzzle because it offers built-in middleware for logging, profiling, caching, and mocking, along with configuration-based client setup via Symfony's YAML files. Its unique selling point is the seamless integration with Symfony's debugging ecosystem, providing real-time insights into HTTP requests directly in the web debug toolbar and profiler.
A bundle integrating Guzzle >=4.0 in Symfony
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Seamlessly displays HTTP request metrics in Symfony's web debug toolbar, profiler panels, and timeline, as shown in the README screenshots, making monitoring effortless.
Allows defining and configuring Guzzle clients directly via Symfony YAML files, simplifying setup without manual code, as highlighted in the documentation.
Includes ready-to-use middleware for logging, profiling, caching, and mocking, extending Guzzle functionality with minimal setup, per the key features.
Supports Guzzle versions 4.0 and above, with specific bundle versions for Guzzle 6, easing migration for legacy projects.
Service descriptions are only available in the unsupported 1.x branch, limiting structured API definitions in newer versions, as admitted in the README.
Different bundle versions correspond to different Guzzle versions (e.g., 2.x for Guzzle 6, 1.x for Guzzle 4/5), creating maintenance overhead and potential confusion.
Tightly coupled with Symfony's ecosystem; switching frameworks would require significant rework, reducing flexibility for non-Symfony environments.