Pr/dev first 11 through 2dc73cd#7
Merged
Merged
Conversation
… and metadata responses
- Updated the edge WAF and rate-limit rules to serve a self-hosted browser verification page instead of a simple block response. - Introduced a challenge token mechanism with configurable difficulty levels for browser verification. - Enhanced the clearance cookie handling to include challenge tokens and proof-of-work validation. - Modified the emergency protection profile to challenge all visitors during attacks. - Updated documentation to reflect the new challenge system and its configuration options. - Added tests to verify the new challenge and clearance functionalities.
- Introduced `challenge_difficulty` field to WAF and rate-limit rules, allowing configuration of challenge levels from 1 to 6. - Updated validation logic to ensure `challenge_difficulty` is within the specified range. - Enhanced API and database schema to support the new parameter. - Modified related tests and documentation to reflect the changes in challenge difficulty handling.
…date related API documentation
…endpoints - Added new API endpoints for managing waiting room policies, including retrieval, update, and emergency activation/deactivation. - Introduced a new WaitingRoomPolicy interface in TypeScript to define the structure of waiting room policies. - Created a new Vue component for the waiting room tab in the domain detail view, allowing users to manage waiting room settings. - Implemented backend logic for waiting room functionality, including ticket issuance and admission control. - Updated OpenAPI documentation to reflect new waiting room endpoints. - Added database migration for waiting room policies table. - Enhanced security documentation to include waiting room admission mechanisms. - Updated setup instructions to include new environment variables for waiting room configuration. - Added CI phase for testing waiting room features and ensuring proper functionality.
… and debug features - Added new cache settings to the database schema for methods, status codes, headers, cookies, and key dimensions. - Updated the API and dashboard to expose new cache settings and provide a cache key preview. - Enhanced edge caching logic to respect new cache settings and provide debug headers. - Created tests to ensure cache correctness and validate new features. - Updated documentation to reflect changes in cache settings and usage.
- Marked Phase 7 as complete in the roadmap with detailed status and tracking information. - Updated API documentation to reflect changes in origin roles and added new health observation endpoints. - Enhanced architecture documentation to clarify origin routing and health observation mechanisms. - Modified CDN setup instructions to use 'primary' role for origins instead of 'origin'. - Adjusted examples to align with new origin role definitions. - Improved troubleshooting documentation to include guidance on drained origins and health checks. - Updated error handling and metrics logging in OpenResty Lua scripts to reflect new origin roles and health checks. - Implemented origin selection logic to prioritize primary origins and handle backups appropriately. - Added new database migration for Phase 7, introducing resilience controls and health observation tables. - Created tests to validate new origin resilience features and ensure API and schema consistency. - Introduced an origin health checker to actively monitor and report origin health status.
- Added CdnConfigSnapshotsPruneCommand for managing config snapshots. - Enhanced config_state schema with new columns for snapshot management. - Updated public_index.php to include new snapshot routes with pagination and history checks. - Modified API documentation to reflect changes in config snapshot endpoints. - Introduced logic to mark the config as dirty on updates, preserving the active snapshot. - Added tests for new snapshot features and ensured legacy behavior is maintained. - Updated docker-compose and deployment scripts to support new environment variables for snapshot management.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Type Of Change
Validation Commands Run
Screenshots
For dashboard changes, attach screenshots or explain why they are not needed.
Security Considerations
Documentation Updated
Breaking Changes
Deployment Impact