Weave Code
Trailing Slash Laravel Package
middlewares/trailing-slash
Laravel middleware that normalizes trailing slashes by redirecting URLs to your preferred format, with configurable behavior, query-string preservation, and clean handling of requests that already match.
Middleware to normalize the trailing slash of the uri path
Frequently asked questions about Trailing Slash
- What does middlewares/trailing-slash do for a Laravel application?
- It normalizes the URL form by redirecting requests to either always include or always remove the trailing slash, based on your configured policy. That helps keep canonical URLs consistent for SEO, analytics, and cache keys. In Laravel it runs as middleware in the HTTP stack and preserves the query string while avoiding internal redirect loops.
- Is middlewares/trailing-slash a native Laravel package or PSR-15 middleware?
- The package is best treated as framework-agnostic PSR-15 middleware, not a Laravel service provider with a config file. Laravel's HTTP kernel uses handle($request, Closure $next), so you need a PSR-7 implementation and a PSR-15-to-Laravel bridge or a thin adapter. The Laravel-native wording in the description should be validated against the actual README before adoption.
- Which Laravel and PHP versions can use middlewares/trailing-slash?
- The integration assessment places it on PHP 8.1+ with Laravel 10, 11, or 12 through an adapter. Native use is for PSR-15 stacks such as Slim, Mezzio, or custom PSR-7 workers. Confirm the supported PSR-15 and PSR-7 versions in the package CI before committing.
- How do I install and register middlewares/trailing-slash in Laravel?
- Install it with Composer, then register it as global middleware that runs before routing so it can catch unmatched paths. Because Laravel is not PSR-15 native, you must add a bridge or adapter class and ensure it executes early enough to short-circuit the request. Check the README for the exact adapter and registration example.
- How do I configure trailing-slash add versus remove behavior?
- The middleware is described as configurable for either always adding or always removing the trailing slash, with a configurable redirect status code. You set the policy once and the middleware compares each request path against it. Verify how the root path and edge cases such as double slashes or file extensions are handled.
- Can I dry-run or test middlewares/trailing-slash before enforcing redirects in production?
- There is no built-in dry-run or log-only mode in the package description, so you will likely wrap it or add logging to observe would-be redirects. Test in staging against root, multi-slash, percent-encoded, and file-extension paths. Also verify query-string preservation and redirect status codes in your adapter.
- Will middlewares/trailing-slash break signed URLs and email verification links?
- It can, and this is the highest-severity risk for Laravel deployments. Signed URLs, email verification links, password-reset links, and any HMAC validated over the exact path will fail when the path is rewritten. Exempt signed routes from the middleware or avoid enforcing a slash policy on those endpoints.
- Is it safe to run middlewares/trailing-slash on API routes and POST requests?
- A 301 redirect on a POST request is typically converted to a GET by clients, which can break API behavior. The described package does not offer per-method exemption, so API surfaces need 308 semantics or an explicit bypass. Restrict enforcement to GET and HEAD, or place API routes outside the middleware stack.
- Does middlewares/trailing-slash work with a CDN, load balancer, or proxy that rewrites slashes?
- It can conflict with an upstream CDN or load balancer that already adds or removes slashes, producing redirect chains or loops. Align the canonicalization policy across all layers and test X-Forwarded-Proto and X-Forwarded-Host behavior. A single redirect layer is safer than two systems enforcing different rules.
- Should I buy middlewares/trailing-slash or write a custom Laravel middleware?
- The behavior is roughly a 50-line first-party middleware, so evaluate it as build-versus-buy rather than against doing nothing. The package shows low adoption and maintenance signals, including 32 stars, a single 2025 release, and an unknown repository, so bus factor and provenance matter. Adopt it only if it survives your edge-case, signed-URL, and proxy tests; otherwise keep the canonicalization policy in your own codebase.
Weaver
How can I help you explore Laravel packages today?