saritasa/laravel-middleware

This package is abandoned and no longer maintained. No replacement package was suggested.

Saritasa middleware for Laravel

2.1.3 2024-08-02 12:41 UTC

Requires

• php: >=7.0
• illuminate/http: >=5.0 <12.0
• illuminate/support: >=5.0 <12.0

Requires (Dev)

• phpunit/phpunit: ^6.0
• squizlabs/php_codesniffer: ^3.5

MIT

• Sergey Populov

• middleware
• laravel

README

Middleware classes for Laravel

Laravel 5.x/6.x/9.x

Install the saritasa/laravel-middleware package:

$ composer require saritasa/laravel-middleware

Optionally If you use Laravel 5.4 or less, or 5.5+ with package discovery disabled, add the MiddlewareServiceProvider in config/app.php:

'providers' => array(
    // ...
    Saritasa\Middleware\MiddlewareServiceProvider::class,
)

It will register default aliases (middleware-key) for all middleware classes

Alternatively, you can just register selected middleware classes in App\Http\Kernel.php yourself

See https://laravel.com/docs/middleware#registering-middleware

Available classes

ClassName / middleware-key

ForceHttps / ssl

This middleware has 2 effects:

1. If user tries to access website over HTTP protocol, redirect him to HTTPS.
2. If request already is made over SSL, force HTTPS URL schema for all generated URLs.

Exception: if APP_ENV is set to 'local'.

This solves 2 problems:

1. Application can be accessed via insecure protocol
2. When application is behind proxy or load balancer, which terminates SSL, standard Laravel classes do not detect it correctly, and generate HTTP links to static resources (JS, CSS) - as result browser blocks them as insecure.

NoCache / no-cache

Insert HTTP headers, preventing content caching on proxy or in browser.

AdminAuthenticate / admin

Checks, that user has role = 'admin'. If not, access is denied.

AjaxOnly / ajax-only

If request was not made via AJAX (with XMLHttpRequest), return 'Bad Request' error.

Contributing

1. Create fork, checkout it
2. Develop locally as usual. Code must follow PSR-1, PSR-2 - run PHP_CodeSniffer to ensure, that code follows style guides
3. Cover added functionality with unit tests and run PHPUnit to make sure, that all tests pass
4. Update README.md to describe new or changed functionality
5. Add changes description to CHANGES.md file. Use Semantic Versioning convention to determine next version number.
6. When ready, create pull request

Make shortcuts

If you have GNU Make installed, you can use following shortcuts:

• make cs (instead of php vendor/bin/phpcs) - run static code analysis with PHP_CodeSniffer to check code style
• make csfix (instead of php vendor/bin/phpcbf) - fix code style violations with PHP_CodeSniffer automatically, where possible (ex. PSR-2 code formatting violations)
• make test (instead of php vendor/bin/phpunit) - run tests with PHPUnit
• make install - instead of composer install
• make all or just make without parameters - invokes described above install, cs, test tasks sequentially - project will be assembled, checked with linter and tested with one single command

Resources

• Bug Tracker
• Code
• Changes History
• Authors