Hi @spowell16
I hope you’re well today!
On a broken links list page you should see a “Details” link right below the “403 forbidden” status label, if you hover over that status.
Once you click on that link you should see additional information in two columns. On the right there should be “Response headers” and “request headers” listed. Could you take a look there and share them for 1-2 example “403 forbidden” reported links?
Pleas also share the those links.
This should help us find out why they are reported this way.
As for them reappearing after they are marked as not-broken: did you try to purge all caches (especially server-side; I believe there should be object cache which is something that might affect how/what information is fetched from database) after marking these links?
Kind regards,
Adam
Hi Adam
Thank you for your reply, see below:
Example 1 – https://www.winsightgrocerybusiness.com/industry-partners/we-are-resilient-industry-confident-supply-challenges-can-be-met-amid-covid-19
Response headers
================
HTTP/2 403
server: awselb/2.0
date: Sun, 07 Mar 2021 02:15:57 GMT
content-type: text/html
content-length: 520
Request headers
================
GET /industry-partners/we-are-resilient-industry-confident-supply-challenges-can-be-met-amid-covid-19 HTTP/2
Host: www.winsightgrocerybusiness.com
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36
accept: */*
referer: https://cfea.com
connection: close
range: bytes=0-2048
Response HTML
================
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
Link is broken.
Example 2 – https://www.restaurantbusinessonline.com/operations/states-ease-liquor-laws-help-restaurants
Response headers
================
HTTP/2 403
server: awselb/2.0
date: Sun, 07 Mar 2021 01:58:17 GMT
content-type: text/html
content-length: 520
Request headers
================
GET /operations/states-ease-liquor-laws-help-restaurants HTTP/2
Host: www.restaurantbusinessonline.com
user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36
accept: */*
referer: https://cfea.com
connection: close
range: bytes=0-2048
Response HTML
================
<html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
Link is broken.
These links aren’t broken so I’ve clicked the link for not broken and everyday they re-appear as broken. We recently moved to a new server so caching won’t resolve this. I’m wondering if our server is being blocked by these news outlets?
Thank you for any help you can provide.
Hi @spowell16,
Thanks for sharing the details. I don’t see the URLs should be causing any issue. From the given information, the server is blocking the response and hence the issue.
ould you please double-check with your hosting provider whether the user-agent listed in the above is getting blocked by your host or not? Please do share the above details with your hosting provider too?
That could also be one of the cases for such an issue to occur. Please do check and let us know how that goes.
Kind Regards,
Nithin
We deactivated the plugin, flushed the cache at the server level and then reactivated the plugin and so far we are not receiving anymore forbidden messages so I think its resolved now.
Hi there @spowell16
That’s excellent news! Thanks for confirming. 🙂
If it happens again, don’t hesitate to re-open this topic and we’ll jump right back in with you.
Cheers!
Patrick
