Total Lines | 14 |
Code Lines | 2 |
Lines | 0 |
Ratio | 0 % |
Changes | 0 |
1 | <?php |
||
9 | Route::get('firewall/info', function () { |
||
|
|||
10 | return [ |
||
11 | 'package_name' => 'Laravel - Firewall', |
||
12 | 'description' => 'Laravel Firewall package detects unknown ip addresses based on |
||
13 | blacklist and whitelist ip addresses. Whitelist and Blacklist are two configuration options |
||
14 | any one of them you can set to TRUE based on your requirement. For example if you set blacklist |
||
15 | to TRUE and have added some ip addresses to blacklist then in that case any request to the |
||
16 | application will be blocked by the firewall from those ip addresses that listed in blacklist. |
||
17 | If you have added them to whitelist only the request from the whitelisted ips can be accepted |
||
18 | and remaining all requests will be blocked by the firewall. If you set both black and whitelist |
||
19 | to TRUE then in that case the preference will be given to blacklist', |
||
20 | 'latest_release' => '2.2.1', |
||
21 | 'stable_version' => '2.2.1', |
||
22 | 'author' => 'Someshwer Bandapally<[email protected]>', |
||
23 | ]; |
||
29 |
The issue could also be caused by a filter entry in the build configuration. If the path has been excluded in your configuration, e.g.
excluded_paths: ["lib/*"]
, you can move it to the dependency path list as follows:For further information see https://scrutinizer-ci.com/docs/tools/php/php-scrutinizer/#list-dependency-paths