Plugin Author
AITpro
(@aitpro)
This is a new check that was added in BPS. There is a known issue with BPS blocking HEAD Requests that will interfere with the Broken Link Checker plugin. Either click on the link in the displayed BPS Alert or click this link to fix the issue.
http://forum.ait-pro.com/forums/topic/broken-link-checker-plugin-403-error/
Plugin Author
AITpro
(@aitpro)
To Reset Dismiss Notices click the Reset/Recheck Dismiss Notices button on the S-Monitor page.
This part of the message needs to be corrected and should say
“To Reset Dismiss Notices click the Reset/Recheck Dismiss Notices button on the Security Status page.”
This will be corrected in the next BPS version.
I had no problems before update, I should add that .htaccess code?
If I don’t fix the code and I reset Dismiss Notices.. Could I have any problem in the future? The broken link checker was working fine.. so, what could happen?
Plugin Author
AITpro
(@aitpro)
Ok well if you are not experiencing any problems then yep just dimiss the notice. It may be the HEAD Request issue no longer exists. I will test the BLC plugin and see if it is doing things differently now. What folks have reported in the past is they see execessive Security Log errors in the BPS Security Log. If you are not seeing that then you can just dismiss the notice.
Plugin Author
AITpro
(@aitpro)
Yep, BLC is still making a HEAD Request and then if that fails it has other fallbacks. So in other words, the 403 error that is logged is just a nuisance error. BLC would not be prevented from doing what it needs to do. So the BLC Dimiss notice is still valid. Resolved.
if ( $nobody ){
//If possible, use HEAD requests for speed.
curl_setopt($ch, CURLOPT_NOBODY, true);
} else {
//If we must use GET at least limit the amount of downloaded data.
curl_setopt($ch, CURLOPT_HTTPHEADER, array('Range: bytes=0-2048')); //2 KB
}
