I'm planning to use this package for a different purpose: implement custom behavior for whitelisted IPs.
Background:
I'm currently applying middleware to check client IP address and putting some values to the request object depending on if they're listed in allowed IPs or not. My approach has been growing bulky lately. This package seems to do it faster than my approach.
I've tested in a very messy way that, the same thing can be accomplished using this package by altering the behavior of either the Filter or the Responder. I will be testing it against my live application as soon as possible.
Proposal:
We could pass in a custom Filter or Responder in config/firewall.php.
First check if a custom class was provided for a Filter or a Responder.
If there is one, call it from the whitelist middleware.
If not, fallback to defaults.
I can go ahead and try to implement that if such functionality would be useful to others as well.
I'm planning to use this package for a different purpose: implement custom behavior for whitelisted IPs.
Background:
I'm currently applying middleware to check client IP address and putting some values to the request object depending on if they're listed in allowed IPs or not. My approach has been growing bulky lately. This package seems to do it faster than my approach.
I've tested in a very messy way that, the same thing can be accomplished using this package by altering the behavior of either the
Filter
or theResponder
. I will be testing it against my live application as soon as possible.Proposal:
config/firewall.php
.Filter
or aResponder
.I can go ahead and try to implement that if such functionality would be useful to others as well.
Please elaborate.