Add excludedPathPatterns for bypassing geoblock checks #107
+299
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Introduces the excludedPathPatterns config option, allowing requests matching specified regex patterns (against the full domain+path) to bypass all geoblock checks. Updates the middleware logic, configuration, and documentation, and adds comprehensive tests for various exclusion scenarios and invalid patterns.
Just for some context, this is is useful when you have multiple sites behind a proxy, but one of them needs to accept webhooks for example. In my specific setup, i am running geoblock on a https://coolify.io server, one of the features is automatic LetsEncrypt cert generation, but with geoblock enabled, it wont generate the certs and they dont have a list of hosts to exclude. Another site i am running, requires webhooks for whatsapp messages, again the provider doesnt specify their hosts so i would like to allow all traffic.