-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature: Expect Protect endpoints to support configuration request methods (all / get / post / put / delete / ...) #129
Comments
@ZhongxuYang this is a really cool feature. Thanks for suggesting it! |
#135) * #129: Add Request Method to Protect endpoints * Regenerate i18n * Refactor protect-endpoints-view * Add unit tests for Protect endpoints --------- Co-authored-by: nicumicle <[email protected]>
@nicumicle Hi there! I just uploaded the Zip file to test
I understand this feature is still under development - just wanted to make sure you"re aware of these issues. Thanks for your quick response on this! 😊 |
Hi @ZhongxuYang , I did some tests, and found a small bug. Can you please give it another try? |
This error is generated by the "All WordPress endpoints checks for JWT Authentication" option from General settings. If this option is enabled, the plugins will search for a JWT in the query parameters/headers/Sesstion/Cookies. You can read more here. |
This plugin is awesome! But I have a little suggestion:
Expect Protect endpoints to support configuration request methods (all / get / post / put / delete / ...), because some wordpress plugins use request methods to distinguish different services, not just paths. 😊
Usage Scenario:
/wp-json/forum
does not validate the user, but needs to validate the user for put/post/delete.The text was updated successfully, but these errors were encountered: