• Whenever I try to purge a page that contains a shortcode that contains a Microsoft Dynamics 365 Marketing Form – I just an almost blank page that just say “no referrer” with the URL looking something like this: https://[READACTED]/wp-admin/admin.php?LSCWP_CTRL=purge&LSCWP_NONCE=6b45e76b00&litespeed_type=purge_front

    Other pages work fine so I guess there is some conflict between the content on the page and the ‘purge this page’ function. Unfortunately, I do not know when the issue was introduced.

    I use WP 7.0.4 and LS Cache plugin 7.9.

    Any idea how to investigate or fix the issue? Any ideas for what could cause the conflict?

    • This topic was modified 23 hours, 1 minute ago by gabbsmo.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support litetim

    (@litetim)

    @gabbsmo please send a report to Litespeed.
    This can be done from LSC => Toolbox => Report => Click on “Send to Litespeed”
    And share the ID generated.

    Thank you

    Thread Starter gabbsmo

    (@gabbsmo)

    @litetim report number: ZKYGXKPT

    Plugin Support litetim

    (@litetim)

    @gabbsmo
    I see you have a stage site.
    Please add this code https://pastebin.com/3ETU1kBL
    You can make it as a plugin or simply add to functions.php
    Instead of the blank no referer page, a full request dump + diagnosis. Please paste these logs(maybe use pastebin too).

    Thread Starter gabbsmo

    (@gabbsmo)

    @litetim Here is the dump: https://pastebin.com/6cJK4bEK

    It says that the referrer header is missing and that you need to purge manually from the dashboard. Is this expected? If yes, where can I post a feature request?

    It would be good if the ‘purge this page’ functions and possible others were not dependent on the referrer header. There are many things that can interfer with it. Something less error prone like a query parameter would be nice. Example: /wp-admin/admin.php?LSCWP_CTRL=purge&LSCWP_NONCE=[REDACTED]&litespeed_type=purge_front&litespeed_redirect_to=/path/to/purged/page

    PS

    I suspected that my browser’s ad blocker or my site’s cookie consent plugins could interfer but the error reproduces with these disabled as well. Maybe it is the browser itself messing with the headers.

    The debug script had a syntax error. Here is the version I used in the end: https://pastebin.com/wew0dLsN

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.