You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible that a user of the library may wish to use our X-Forwarded-For and Forwarded handling/parsers, but choose which IP to use in a different way (than "rightmost non-private", "trusted count", etc.). So they would like strategies like:
Those would choose the left/rightmost IP for which filter returns true.
I don't want to add this just because someone "might" want them, but if anyone has any solid examples/use cases, please let us know here.
If we do add this, we might want to also export privateAndLocalRanges and/or isPrivateOrLocal. Those are likely to be needed by a custom filter. (Possibly other helpers, like goodIPAddr?)
The text was updated successfully, but these errors were encountered:
It's possible that a user of the library may wish to use our
X-Forwarded-For
andForwarded
handling/parsers, but choose which IP to use in a different way (than "rightmost non-private", "trusted count", etc.). So they would like strategies like:Those would choose the left/rightmost IP for which
filter
returns true.I don't want to add this just because someone "might" want them, but if anyone has any solid examples/use cases, please let us know here.
If we do add this, we might want to also export
privateAndLocalRanges
and/orisPrivateOrLocal
. Those are likely to be needed by a custom filter. (Possibly other helpers, likegoodIPAddr
?)The text was updated successfully, but these errors were encountered: