Weave Code
Proxy Sdk Laravel Package
redirectionio/proxy-sdk
PHP SDK for Redirection.io's proxy, helping PHP applications apply managed redirect and routing rules. Integrate redirects, status codes, and URL handling into your app via a lightweight client API that communicates with the Redirection.io proxy.
PHP Common code for redirection.io proxy
Frequently asked questions about Proxy Sdk
- What is redirectionio/proxy-sdk used for?
- redirectionio/proxy-sdk is a PHP SDK that sends request context such as host, scheme, URI, and user agent to a locally running redirection.io agent. The agent evaluates rules managed in the redirection.io dashboard and returns a redirect target, status code, or no-match result. Your PHP application remains responsible for sending the actual response.
- Does redirectionio/proxy-sdk work with Laravel?
- It is framework-agnostic PHP, so it can be called from a Laravel application, but the provided context does not describe a first-party Laravel service provider or middleware. You would need to wire the client into your own middleware or request flow and handle the returned action. Before committing, confirm with redirection.io whether this SDK is the sanctioned Laravel integration path or primarily internal proxy code.
- How do I install redirectionio/proxy-sdk?
- Install it with Composer using composer require redirectionio/proxy-sdk. Because the package has a 2020-era history and only a recent v0.4.0 minor release, check its composer.json constraints and run composer why-not against your Laravel and PHP versions. Do not assume installation success means production compatibility.
- Which PHP and Laravel versions does redirectionio/proxy-sdk support?
- The context does not state explicit PHP or Laravel version constraints, and there is no clear PHP 8.x support statement. The original concern is that a 2020-era dependency graph may collide with Laravel 10 or 11 on PHP 8.2 or 8.3. Verify with composer why-not and ask the vendor for a supported-version statement before relying on it.
- How does the SDK communicate with the redirection.io agent?
- The SDK communicates with the redirection.io agent over a socket for low-latency lookups. It sends the full request context so the agent can select the best matching rule and return a redirect or passthrough decision. This means a local agent must be running and reachable from your application.
- How do I configure the socket connection to the agent?
- Configuration is centered on the client connection to the local agent socket, but the exact option names are not detailed in the provided context. v0.4.0 adds a way to deactivate the persist flag on client connections, which affects connection reuse. Review the package source and test persistence behavior against your load balancer or NAT idle timeouts.
- What production risks should I check before using it on the request path?
- The main risk is request-path blast radius: a defect can cause site-wide redirect failures rather than a localized feature bug. Maintenance is also a concern because one minor release in five years is not a security or PHP-version support commitment, and the API contract has little visible community pressure. v0.4.0 changes connection persistence semantics, which can fail quietly through latency drift, socket exhaustion, or resets, so test p95 latency and fail-open versus fail-closed behavior.
- How should I test redirect behavior with redirectionio/proxy-sdk?
- Run a local redirection.io agent and test representative request contexts, asserting redirect targets, status codes, and no-match results. Add failure tests for an unavailable agent, socket timeouts, and connection persistence on and off if you use v0.4.0. In Laravel, wrap the client behind your own service so feature tests can fake decisions without requiring the agent.
- Is redirectionio/proxy-sdk actively maintained?
- v0.4.0 is a new semver-minor release, so the package is not accurately described as having no releases since 2020. However, a one-line release note with no changelog, migration guidance, or PHP 8.x support statement is weak evidence of renewed maintenance. Check whether the repository is still archived and confirm stars, dependents, and vendor support before treating it as active.
- What alternatives should I consider for Laravel redirect management?
- Prefer the highest integration layer the vendor supports: managed edge or CDN first, then the redirection.io agent, then a first-party Laravel or PSR-15 middleware, and only then the raw SDK. Ask redirection.io whether a maintained first-party Laravel integration exists and what the supported production entry point is. Until that is confirmed, treat redirectionio/proxy-sdk as a reference implementation to read rather than a dependency to ship.
Weaver
How can I help you explore Laravel packages today?