You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
move limit_req option to Wordpress or make it universal
Feature description
The limit_req option is currently under "Global -> Security" but only applies to Wordpress. Either move it to the Wordpress options or make it more universal. This could be done by adding this code #380 (comment)
to every webpage that the user creates.
How the feature is useful
At the moment, if you create multiple (or even a single) page and none of them are Wordpress pages, one could wrongly assume that there is some kind of rate limiting settings at work. It is under "Global -> Security" but does not say that it only applies to Wordpress pages.
If you are not careful and don't check what the option is actually doing, one could be mislead and think that there is some rate limiting going on without realizing that there is none. This is especially true because it creates a limit zone, but you have to realize or check that this zone never actually gets used.
By moving this to the Wordpress options, this could prevent misunderstandings. Alternatively it could applied to every site by implementing @webdev3301 code snippets to every page. By adding it to every page, it would really become a setting that belongs to "Global -> Security" because it would become a global setting.
The text was updated successfully, but these errors were encountered:
Feature request
move limit_req option to Wordpress or make it universal
Feature description
The limit_req option is currently under "Global -> Security" but only applies to Wordpress. Either move it to the Wordpress options or make it more universal. This could be done by adding this code
#380 (comment)
to every webpage that the user creates.
How the feature is useful
At the moment, if you create multiple (or even a single) page and none of them are Wordpress pages, one could wrongly assume that there is some kind of rate limiting settings at work. It is under "Global -> Security" but does not say that it only applies to Wordpress pages.
If you are not careful and don't check what the option is actually doing, one could be mislead and think that there is some rate limiting going on without realizing that there is none. This is especially true because it creates a limit zone, but you have to realize or check that this zone never actually gets used.
By moving this to the Wordpress options, this could prevent misunderstandings. Alternatively it could applied to every site by implementing @webdev3301 code snippets to every page. By adding it to every page, it would really become a setting that belongs to "Global -> Security" because it would become a global setting.
The text was updated successfully, but these errors were encountered: