Update changelog and tested up to version

CHANGELOG.md

@@ -1,5 +1,13 @@
 ## Changelog ##
 
+### 2.11.7 ###
+
+* **English**
+  * Tweak: Use SCRIPT_NAME instead of REQUEST_URI to check path
+
+* **Deutsch**
+  * Tweak: Verwende SCRIPT_NAME anstelle von REQUEST_URI, um den Pfad zu prüfen
+
 ### 2.11.6 ###
 * **English**
   * Fix: Delete missed out option on uninstall (Thanks @okvee!)

antispam_bee.php

@@ -9,7 +9,7 @@
  * Domain Path: /lang
  * License:     GPLv2 or later
  * License URI: http://www.gnu.org/licenses/gpl-2.0.html
- * Version:     2.11.6
+ * Version:     2.11.7
  *
  * @package Antispam Bee
  **/
@@ -1127,6 +1127,7 @@ public static function upgrade_notice( $data ) {
 	 *
 	 * @since  0.1
 	 * @since  2.6.3
+	 * @since  2.11.7 Switching from REQUEST_URI to SCRIPT_NAME for the check
 	 */
 	public static function precheck_incoming_request() {
 		// phpcs:disable WordPress.Security.NonceVerification.Missing
@@ -1161,6 +1162,7 @@ public static function precheck_incoming_request() {
 	 * @since  0.1
 	 * @since  2.6.3
 	 * @since  2.10.0 Refactoring of code if pings are allowed and if is ping
+	 * @since  2.11.7 Switching from REQUEST_URI to SCRIPT_NAME for the check
 	 *
 	 * @param   array $comment  Untreated comment.
 	 * @return  array $comment  Treated comment.

readme.txt

@@ -3,9 +3,9 @@
 * Tags:              anti-spam, antispam, block spam, comment, comments, comment spam, pingback, spam, spam filter, trackback, GDPR
 * Donate link:       https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=TD4AMD2D8EMZW
 * Requires at least: 4.5
-* Tested up to:      6.5
+* Tested up to:      6.7
 * Requires PHP:      5.2
-* Stable tag:        2.11.6
+* Stable tag:        2.11.7
 * License:           GPLv2 or later
 * License URI:       https://www.gnu.org/licenses/gpl-2.0.html
 
@@ -65,7 +65,7 @@ Antispam Bee works best with default WordPress comments. It does not help to pro
 Antispam Bee works best with default WordPress comments. It is not compatible with Jetpack, wpDiscuz or Disqus Comments as those plugins load a new comment form within an iframe. Thus Antispam Bee can not access the comment form directly.
 
 ### Does Antispam Bee work with AJAX comment plugins or similar theme features?
-Whether Antispam Bee works with a comment form submitted via AJAX depends on how the AJAX request is made. If the request goes to the file that usually also receives the comments, Antispam Bee could work with it out of the box (the [WP Ajaxify Comments](https://wordpress.org/plugins/wp-ajaxify-comments/) plugin does this, for example). 
+Whether Antispam Bee works with a comment form submitted via AJAX depends on how the AJAX request is made. If the request goes to the file that usually also receives the comments, Antispam Bee could work with it out of the box (the [WP Ajaxify Comments](https://wordpress.org/plugins/wp-ajaxify-comments/) plugin does this, for example).
 
 If the comments are sent to the `admin-ajax.php`, the `antispam_bee_disallow_ajax_calls` filter must be used to run ASB for requests to that file as well. If the script does not send all form data to the file, but only some selected ones, further customization is probably necessary, as [exemplified in this post by Torsten Landsiedel](https://torstenlandsiedel.de/2020/10/04/ajaxifizierte-kommentare-und-antispam-bee/) (in German).
 
@@ -95,6 +95,9 @@ A complete documentation is available on [pluginkollektiv.org](https://antispamb
 
 ## Changelog ##
 
+### 2.11.7 ###
+  * Tweak: Use SCRIPT_NAME instead of REQUEST_URI to check path
+
 ### 2.11.6 ###
   * Fix: Delete missed out option on uninstall (Thanks @okvee!)
   * Tweak: Minor i18n improvements (Thanks Pedro!)