PHPackages                             writecl/burp - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Search &amp; Filtering](/categories/search)
4. /
5. writecl/burp

ActiveLibrary[Search &amp; Filtering](/categories/search)

writecl/burp
============

Simple PHP router that works with query-string and uri-segments, laravel filter system

4.0.0(6y ago)01.8k1MITPHP

Since Mar 26Pushed 6y agoCompare

[ Source](https://github.com/writecl/burp)[ Packagist](https://packagist.org/packages/writecl/burp)[ Docs](https://github.com/writecl/burp)[ RSS](/packages/writecl-burp/feed)WikiDiscussions master Synced 1w ago

READMEChangelogDependencies (1)Versions (3)Used By (1)

Burp
====

[](#burp)

Simple php **Router** that can work with "URI", "QUERY STRING", or both.
It also has a simple **Event** Listener implementation (to fire or queue application events).

You can use Burp in your preferred framework (Including laravel), It does not pretend to be the only router, It just check your urls then fire or queue your events.

why
---

[](#why)

The idea is to have an "all in one" router,filter,event listener.
I'ts a way to build event-driven widgets and define a flexible "semantic" in application urls

Burp can power widgets that works driven by *uri-segments*,*query-string* or both, without the need to have a classic controller.

Installation
------------

[](#installation)

install via composer adding `"writecl/burp": "3.0.*"`

if you're using laravel add the service provider in config/app.php:

```
'providers' => array(
    ...
    'Writecl\Burp\BurpServiceProvider',
)

```

usage
-----

[](#usage)

Burp is similar to any other PHP router, but it can also behave as a filter.
There are two main differences you need to know:

- a route rule can be **strict** or **not strict** (It means: "exact match", or "partial match" i.e. a non strict rule can match some uri-serment or some query-string parameter)
- rules are non-blocking, It means that a single http request can trigger more than one route

samples
-------

[](#samples)

```
