Weave Code
Http Logger Bundle Laravel Package
forci/http-logger-bundle
A Symfony bundle that captures and logs HTTP requests and responses, helping you debug APIs, trace outgoing calls, and inspect traffic in your application. Configurable handlers let you control what gets recorded and where the logs are written.
At a glance
Frequently asked questions about Http Logger Bundle
- Can I use forci/http-logger-bundle in Laravel?
- No, not as a native Laravel package. forci/http-logger-bundle is a Symfony bundle that registers through Symfony's bundle and DI lifecycle, and the provided material shows no Laravel facade, config publish, auto-discovery, or Artisan integration. Using it in Laravel would require custom service-provider glue that you own and re-test on PHP and Guzzle upgrades.
- How do I install forci/http-logger-bundle?
- Install it with Composer and register it as a Symfony bundle in your application's bundle configuration. The overview does not document a Laravel installation path, package discovery, or config publishing. For Laravel, treat any install as a custom integration spike rather than a supported setup.
- Does forci/http-logger-bundle support Laravel 10 or Laravel 11?
- The package does not claim Laravel 10 or Laravel 11 support; it is described as a Symfony bundle. Laravel has no equivalent bundle registration lifecycle, so it will not auto-register or expose Laravel-native configuration. Confirm compatibility against your pinned PHP and HTTP client versions before relying on it.
- What does forci/http-logger-bundle log and which logger does it use?
- The overview says it can log requests, responses, and timing metadata through configurable middleware, with pluggable PSR-3 logger support. Exact defaults, field names, and whether correlation IDs are included are not specified in the provided material. Read the source and configuration reference to confirm the captured payload.
- Does forci/http-logger-bundle redact Authorization headers and request bodies?
- Do not assume default redaction. The overview says sensitive-header and payload handling is left to your logging configuration, so Authorization headers, cookies, tokens, and request bodies may be recorded unless you explicitly prevent it. Verify redaction behavior with synthetic secrets before enabling it anywhere real traffic flows.
- Is forci/http-logger-bundle licensed for commercial use?
- The TPM assessment flags the license as NOASSERTION, meaning GitHub could not detect a recognized license. Without a clear grant, copyright defaults to all rights reserved, so commercial use, modification, and redistribution need legal review of the actual LICENSE text. Resolve this before engineering effort, not after.
- Does forci/http-logger-bundle work with Laravel's HTTP client or Guzzle?
- Unknown from the provided material, and this is the key integration question. The bundle is Symfony middleware, while Laravel's HTTP client resolves through Guzzle via Illuminate\Http\Client. Only a PSR-3 decorator or PSR-18 client wrapper would likely port cleanly, so inspect the source before spending time.
- What are the best alternatives for HTTP logging in Laravel?
- Laravel already exposes interception points such as Illuminate\Http\Client\Events\RequestSending, ResponseReceived, and ConnectionFailed, plus Guzzle middleware for gaps. Telescope and Pulse cover development and staging visibility, while a Monolog channel with a correlation-ID processor can handle production logging. A first-party implementation is typically 50 to 80 lines with full control over redaction and sampling.
- Is forci/http-logger-bundle safe to run in production?
- Treat it as risky until redaction, body-size limits, buffering versus streaming, and sampling support are proven. HTTP logs often contain credentials and personal data, so an unaudited logger becomes a retention and compliance liability. The reported 0 stars, 0 dependents, and bus factor of one are also weak adoption signals for production.
- How do I test HTTP logging and redaction before deploying?
- Use a local PSR-3 spy logger, synthetic requests, and fake tokens to assert exactly which headers, bodies, and timing fields are recorded. Test redaction, maximum body size, sampling, and failure behavior when the logger is unavailable. Do not send real credentials or production traffic through an unverified integration.
Weaver
How can I help you explore Laravel packages today?