Weave Code
Proxy Symfony Laravel Package
redirectionio/proxy-symfony
Official Symfony integration for Redirection.io's proxy. Route traffic through Redirection.io to manage redirects, URL rewrites, and 404 tracking from a dashboard, with minimal app changes and Symfony service configuration.
RedirectionIO Proxy for Symfony
Frequently asked questions about Proxy Symfony
- What is redirectionio/proxy-symfony used for?
- It is an official Symfony bundle that integrates redirection.io redirect management into a Symfony application. It hooks into the HTTP kernel to evaluate incoming requests against redirection.io rules and return configured redirects or HTTP responses. That lets teams manage redirects centrally outside application code.
- Does redirectionio/proxy-symfony work with Laravel?
- No, redirectionio/proxy-symfony is an official Symfony integration, not a Laravel package. The TPM notes specifically ask whether it follows Laravel conventions such as service providers, config publishing, container bindings, and facades. Laravel teams should verify compatibility or consider applying redirection.io at the proxy, edge, or web-server layer instead.
- How do I install redirectionio/proxy-symfony with Composer?
- Installation is assumed to be Composer-based, but the provided notes do not include the exact require command or bundle registration steps. Because v0.3.0 is pre-1.0, pin the exact version in Composer and review dependency changes before upgrading. Confirm your Symfony component ranges before modifying composer.lock.
- Which Symfony, PHP, and Laravel versions are supported?
- The notes mention Symfony 4 deprecation fixes in v0.3.0, but they do not include a full PHP, Symfony, or Laravel compatibility matrix. Symfony 4 is end-of-life, so teams on newer Symfony or Laravel releases should confirm supported component ranges. Ask whether there is a roadmap to Symfony 5, 6, or 7 before production adoption.
- How does the bundle evaluate redirection.io rules during a request?
- The bundle fits into the HTTP kernel request/response lifecycle and evaluates incoming requests against your redirection.io rules. When a rule matches, it returns the configured redirect or HTTP response instead of letting the application handle that path. The exact internals are not detailed in the provided excerpt.
- Is redirectionio/proxy-symfony safe for production?
- Treat v0.3.0 as pre-1.0 and not automatically semver-safe despite being a minor release. Validate it in a non-production environment, run your application and integration tests, and canary outbound connection behavior. Keep a rollback to the prior pinned version and confirm the persist flag behavior before production rollout.
- What is the client-connection persist flag in v0.3.0?
- The v0.3.0 notes describe a client-connection persist toggle that affects outbound HTTP connection lifecycle. The materials do not say whether its default is backward compatible or whether disabling it creates a new connection per request. Test both enabled and disabled states for latency, connection reuse, pool exhaustion, and error rates.
- How should I test redirection.io redirects in a Symfony app?
- Run your normal Symfony test suite plus integration tests that exercise real redirection.io rules and expected redirects or HTTP responses. The release notes do not include test coverage details or a published test matrix, so add your own coverage around kernel integration. Also test the persist flag in both states before relying on it.
- What are alternatives to redirectionio/proxy-symfony?
- Alternatives include handling redirects at a reverse proxy, CDN, load balancer, or web server, or writing a custom Symfony kernel listener. The key trade-off is whether redirect management stays centralized outside application code. Confirm whether redirection.io's proxy layer can meet the same operational needs before replacing this bundle.
- How is redirectionio/proxy-symfony maintained and is v0.3.0 stable?
- The release shows active maintenance, but the notes are sparse and v0.3.0 is pre-1.0. Ask for changelog discipline, a dependency support policy, security disclosure process, and clarity on Symfony 4 EOL handling. Without that, maintenance risk is higher than for a stable 1.x package.
Weaver
How can I help you explore Laravel packages today?