documentation new haproxy spoa configuration for captcha redirect #888
Conversation
This file contains hidden or 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
- Replace Lua-based redirect with native HAProxy 302 redirect for allow decisions - Add performance optimization by calling Lua only for ban and captcha remediations - Update both HAProxy configuration examples with the new approach - Add dedicated section explaining the performance benefits - Reduce overhead and improve scalability by minimizing Lua processing
- Remove the standalone Native HAProxy Redirect section - Keep the updated configuration examples with native redirects and performance optimizations
LaurenceJJones
changed the title
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
update configuration example as per crowdsecurity/cs-haproxy-spoa-bouncer#62