Download the PHP package gabbro-php/middleware without Composer
On this page you can find all versions of the php package gabbro-php/middleware. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package middleware
Gabbro - Middleware & Routing
This library provides a middleware execution engine and a routing component for building HTTP services.
It is designed to be simple, explicit, and framework-agnostic — you can drop it into any project and wire up your own request/response handling.
Middleware Engine
At the core is the StackEngine contract, implemented by OrderedStackEngine.
-
Middleware are small units of code that take a
Request, do some work, and then either:- Call the next middleware in the stack, or
- Short-circuit the pipeline and return a
Response.
- Middleware can be registered in a specific order, and can be filtered by HTTP verb flags.
- The engine supports optional exception catching, so uncaught exceptions can be converted into
500 Internal Server Errorresponses.
This gives you a pipeline model where cross-cutting concerns like logging, auth, or body parsing can be layered transparently.
Router
The MiddlewareRouter component acts as both:
- A Router, capable of dispatching requests to controllers based on HTTP verb and URI pattern.
- A Middleware, so it can slot into the stack like any other component.
Features
-
Path patterns:
*wildcard segments.- Placeholders:
{id},{id:int},{slug:alpha}. - Value sets:
{status:[open|closed|pending]}. - Optional segments prefixed with
?.
-
Named routes:
Define routes with a name and later generate the corresponding path with dynamic values (getNamedPath()). -
Binding of route parameters:
When a path matches, placeholders are automatically injected into the request attributes using the key formatbound-{name}.
Example: a route/users/{id:int}will yield$request->getAttribute("bound-id"). - Controller flexibility:
Controllers can be:- A callable (closure or function),
- A class implementing the
Controllerinterface, or - A class name string (which will be instantiated if it implements
Controller).
Composition
Because the router itself is a middleware, you can:
-
Use
OrderedStackEngineto build a layered stack: - Or just use the router directly if you don’t need a full middleware stack:
Philosophy
This library is intentionally minimal:
- No global state — everything is explicit and injectable.
- Small contracts (
Middleware,StackEngine,Router,Controller) define clear extension points. - Predictable behavior — request goes in, response comes out, with optional error handling.
The idea is to give you a solid foundation for building your own micro-frameworks, HTTP services, or experimental backends, without forcing a specific architecture or heavy dependency tree.
