Adlago Posted April 15, 2019 Share Posted April 15, 2019 On this topic, in my ticket after many research, in version 4.4.1, @bfarber said to include a patch in the next version to fix these records errors ... Yes, however, these record log errors continue. 2S119/1 Something went wrong. Please try again. 95.216.197.231 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/14/2019 05:30 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM 2S119/1 Something went wrong. Please try again. 162.243.114.156 /terms/?do=dismiss&ref=aHR0cHM6Ly9ub3BoZWxldC5jb20… 04/13/2019 03:45 PM Adoption of the rule by a guest bot machine that made a session fix from a this bot machine. Next visit from this bot but another machine causes this error - another machine has another session guest but uses an indexed address ... Will the IPS find a solution to this? Link to comment Share on other sites More sharing options...
bfarber Posted April 16, 2019 Share Posted April 16, 2019 We added a rel=nofollow attribute to the link. There is no way to outright block a bot from visiting the URL, but we have instructed search engine spiders not to follow the link in the future. Link to comment Share on other sites More sharing options...
Joy Rex Posted April 16, 2019 Share Posted April 16, 2019 That is, of course if the spider honors the nofollow noindex directives... Link to comment Share on other sites More sharing options...
Makoto Posted April 16, 2019 Share Posted April 16, 2019 Unfortunately, you can't force all spider's to behave properly. Link to comment Share on other sites More sharing options...
bfarber Posted April 17, 2019 Share Posted April 17, 2019 Yes, and it doesn't cause any harm if they do visit the URL when they don't honor the directive. It would generate a log and email, potentially depending upon your configuration, however the default notifications are for level 3 and above (not level 2, which this error is). If they did follow the link with a correct CSRF key, it would simply dismiss the cookie notification terms for the bot. In short, there's no real harm here. We added a nofollow directive to reduce spiders wasting their time with the link unnecessarily. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.