API calls return 403 because of RewriteRule

Hi @volkerharz,

A rewrite rule consists of the following structure:

RewriteRule Pattern Substitution [Flags]

RewriteRule: specifies the RewriteRule directive
Pattern: a PCRE (Perl Compatible Regular Expression) that matches the desired string. You can learn more about regular expressions here.

^ -> Called an anchor, matches the beginning of the string
. -> Matches any single character
* -> Repeats the previous match zero or more times

Substitution: where should the matching requests be sent

A dash (-) means do nothing.

[Flags]: optional parameters to modify the rule. For more information on the available flags and their meanings, see Apache’s documentation on Rewrite Flags.

[F]Forbidden: instructs the server to return a 403 “Forbidden” response to the client.
[L]Last rule: instructs the server to stop rewriting after the preceding directive is processed.

Most likely the API Calls HTTP_USER_AGENT is empty which triggers the RewriteRule.(RewriteCond %{HTTP_USER_AGENT} “^$” [NC,OR]).

+++++ To prevent any confusion, I’m not iThemes +++++

Hi @nlpro you’re awesome! Thank you!

Most likely the API Calls HTTP_USER_AGENT is empty which triggers the RewriteRule.(RewriteCond %{HTTP_USER_AGENT} “^$” [NC,OR]).

Totally makes sense now. Thanks.

Edit: Seems i have to a deactive the default ban list as ithemes keeps overwriting .htaccess.

  • This reply was modified 4 minutes ago by VolkerHarz.
  • This reply was modified 1 minute ago by VolkerHarz.

 

This site will teach you how to build a WordPress website for beginners. We will cover everything from installing WordPress to adding pages, posts, and images to your site. You will learn how to customize your site with themes and plugins, as well as how to market your site online.

Buy WordPress Transfer