Chrome fails to see token

  • Resolved Grzegorz.Janoszka

    (@grzegorzjanoszka)


    8 years, 9 months ago

    I am very happy to use this plugin as it can replace my old security plugin and akismet. I noticed however several false positives a day – normal comments that were classified as spam because of token test failing. I dug into that and I noticed all those comments came from Chrome browser.
    It reminded me another issue I had with css and js files. It seems Chrome does tricks to speed up the page and it servers my website from Google cache or just from local cache and it doesn’t refresh it. I have had this plugin installed for maybe a week, but I saw threads about Chrome keeping displaying old pages for weeks.
    Exemplary thread with other people describing the issue:
    https://productforums.google.com/forum/#!topic/chrome/xR-6YAkcASQ

    Is there any way to remove the token test and relay only on the js and timeouts? I would love to see such option.

    Thank you for a fantastic support!

    https://www.ads-software.com/plugins/wp-simple-firewall/

Viewing 6 replies - 16 through 21 (of 21 total)
  • Plugin Author Paul

    (@paultgoodchild)

    Yes, I believe that that should have by-passed the token checking. I’ll need to recheck the code flow.

    It would be good to know if the caching plugin was interfering though, either way.

    I’ll check the plugin flow and if there’s anything to tweak, I’ll see if I can squeeze it into the 4.17 release.

    Thread Starter Grzegorz.Janoszka

    (@grzegorzjanoszka)

    OK, I have now disabled the caching mechanism of wp-fastest-cache and I have verified it is really off. Last days I had usually 5 or more false spams a day, so I shall have results quite quickly.

    Plugin Author Paul

    (@paultgoodchild)

    I’d be keen to hear if turning off the cache made a difference… I haven’t heard of issues with this feature for years now.

    I’ve tweaked the code a little and setting both timeouts to zero will now effectively turn off checks on the comment token. It’s in the beta ready for download.

    Plugin Author Paul

    (@paultgoodchild)

    Were you able to confirm that the cache plugin was interfering?

    Thread Starter Grzegorz.Janoszka

    (@grzegorzjanoszka)

    I disabled the caching plugin and shortly after I had two false positives. For the next few days everything was fine, and then you pushed the new version of the plugin to WordPress which seems to solve all the issues. Last 50+ spams were 100% spams, no false alarms. I hope it will continue in the future. Fantastic plugin and great support, I am very happy about it and I would like to thank you one more time for everything you do.

    Plugin Author Paul

    (@paultgoodchild)

    Great! very happy to hear it’s working correctly for you now. Hopefully things will remain so ??

    May I ask you to leave us a nice review of the plugin? ??

    Cheers!

Viewing 6 replies - 16 through 21 (of 21 total)
  • The topic ‘Chrome fails to see token’ is closed to new replies.