• Resolved jlebouch76

    (@jlebouch76)


    Hello,

    I use the Real Cookie Banner plugin (RCB) to manage the consents of my website. RCB and NF have run well together for a long time. But today, I’ve discovered something strange. I get a warning Message in the WP backend with the following message:

    Consent cannot be saved in the cookie banner: Website visitors (not logged into WordPress) currently cannot save consents in the cookie banner. This may result in the cookie banner being displayed again each time the website visitor visits a page.

    The consent would be saved via the WP REST API route https://zzzzzzzzzzz.com/wp-json/real-cookie-banner/v1/consent. The following problems with your WordPress installation were detected during the automatic error analysis:

    • HTTP error code 403 has been returned by the server. This indicates that the WP REST API may have been proactively blocked.
    • Response from the server is malformed. This indicates, for example, that another plugin is manipulating the response. In the following, you find the server response:

      Sorry xxxxxxxxx, your request cannot be processed.
      For security reasons, it was blocked and logged.
      If you believe this was an error please contact the
      webmaster and enclose the following incident ID:
      yyyyyy

    What is really weird is that despite this message, the consent with no referrer is actually visible in RCB backend but I don’t know if it’s really stored in the database. Furthermore, the Firewall is not set to block WP Rest API. When I deactivate NF and clear the website cache, the warning message from RCB immediately disappear.

    When I look at the incident ID in NF, I get this: POST /index.php – POST method without Referrer header – [POST] – zzzzzzzzzzzz.com

    Where could the problem be and how to solve it?

    Thanks for your help.

    • This topic was modified 2 years, 1 month ago by jlebouch76.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author nintechnet

    (@nintechnet)

    Go to the “Firewall Policies > Intermediate Policies” tab, and disable the “HTTP_REFERER server variable > Block POST requests that do not have an HTTP_REFERER header” policy. It is disabled by default to prevent scripts from being blocked.

Viewing 1 replies (of 1 total)

The topic ‘[NSFW] POST method without Referer header create Error in other Plugin’ is closed to new replies.