wordfence 403 being erroneously cached by litespeed

  • Resolved matindow

    (@matindow)


    6 years, 7 months ago

    Experiencing an issue where litespeed seems to be caching 403 pages that are generated by wordfence in response to bot traffic and then showing them to all subsequent visitors, even though the litespeed plugin is configured with the “Default 403 Page TTL” set to 0 seconds, which I believe exists specifically to prevent this from happening? The “Purge All” button immediately corrects the issue, which seems to suggest that it is in fact a result of litespeed caching the page rather than some other layer?

    Any help is greatly appreciated,

    Thanks

Viewing 2 replies - 1 through 2 (of 2 total)
  • stanley@litespeed

    (@stanleylitespeed)

    6 years, 7 months ago

    Hi @matindow, can you send us the response header for checking if you hit the 403 cache?

    Plugin Support LiteSpeed Lisa

    (@lclarke)

    6 years, 7 months ago

    Hi @matindow,

    I’m going to mark this topic “Resolved,” due to lack of activity.

    If you still need help, please provide a 403 page response header, so we can see if/how it’s being cached?

    We’ll be happy to reopen the topic if necessary.

    Thanks!

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

The topic ‘wordfence 403 being erroneously cached by litespeed’ is closed to new replies.

Tags