#129: Add support for configuring request methods on Protect endpoints #135
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
nicumicle
changed the title
nicumicle
changed the title
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.
Issue Link
#129
Types of changes
Description
Add a new feature to protect specific endpoints by path, allowing selective access control. For example, this implementation enables you to restrict the POST /wp/wp/posts endpoint (preventing users from creating posts without authentication) while keeping the GET /wp/wp/posts endpoint accessible without authentication.
This MR does not introduce any breaking changes from the previous versions.
Checklist:
composer check-pluginlocally