wordfence missmatch

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author kerryoco

    (@kerryoco)

    ah thanks. It seems to be picking up the differences between files with different letter-cases in the filename, so it’s actually ok. (PLAYER.js, and Player.js). The browsers treat those as separate files but Wordfence isn’t. I’m not sure exactly why your Wordfence is showing that but mine isn’t (I have it installed on a bunch of sites too). I’ll make a note to modify the filenames with the next update to avoid the warning though.

    Do you host on Windows by any chance? If I remember correctly, Windows doesn’t use case in filenames, and if Wordfence is somehow using the OS for filenames, that might be related, and something I should think more about as well

    • This reply was modified 3 months, 2 weeks ago by kerryoco.
    • This reply was modified 3 months, 2 weeks ago by kerryoco.
    Thread Starter 3xploiton3

    (@3xploiton3)

    testing with localhost, windows 11, laragon tools

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.