Add the ability to load ranges from a text file #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add the ability to load IP ranges from a text file and update documentation. * **config.go** - Add a new subdirective `ranges_file` to load ranges from a text file. - Update the `UnmarshalCaddyfile` function to handle the new subdirective. - Update the `Validate` function to validate the ranges loaded from the text file. - Add a check to throw an error if neither `ranges` nor `ranges_file` is specified. * **middleware.go** - Add logic to check if the client IP is in any of the ranges loaded from the text file. * **plugin.go** - Update the `DefenderMiddleware` struct to include a new field `RangesFile`. - Update the `Provision` function to load ranges from the specified text file. * **examples/range_files/Caddyfile** - Add a new example Caddyfile demonstrating the usage of `ranges_file` subdirective. * **examples/range_files/ranges.txt** - Add a new text file containing example IP ranges. * **README.md** - Add documentation for the new `ranges_file` subdirective.
Registers the `defender` directive to be executed before `basicauth`. This ensures that IP restrictions are applied before authentication. Removes redundant `order` directives from Caddyfile examples.
Renamed `DefenderMiddleware` to `Defender` for clarity and consistency. This change affects the struct name, corresponding methods, and documentation. Updated `CONTRIBUTING.md`, `README.md`, and examples to reflect this change. Adjusted error handling in `config.go` to align with Caddy's conventions. Simplified `plugin.go` by removing unnecessary nil check after `UnmarshalCaddyfile`. Removed global `order` directive from `intro.md` and `README.md` as it's now redundant.
Refactor the config scheme
The configuration for the custom responder has been simplified. The `message` field is now directly part of the Defender configuration and is passed to the `CustomResponder`. The responder type is no longer required during setup, streamlining the process.
The configuration for the custom responder has been simplified. The `message` field is now directly part of the Defender configuration and is passed to the `CustomResponder`. The responder type is no longer required during setup, streamlining the process.
…ween Provision & middleware steps!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add the ability to load IP ranges from a text file and update documentation.
config.go
ranges_fileto load ranges from a text file.UnmarshalCaddyfilefunction to handle the new subdirective.Validatefunction to validate the ranges loaded from the text file.rangesnorranges_fileis specified.middleware.go
plugin.go
DefenderMiddlewarestruct to include a new fieldRangesFile.Provisionfunction to load ranges from the specified text file.examples/range_files/Caddyfile
ranges_filesubdirective.examples/range_files/ranges.txt
README.md
ranges_filesubdirective.