]]>Status code Broken URL Ignored Found on
405 Method Not Allowed https://wireless2.fcc.gov/UlsEntry/licManager/login.jsp no https://rarclub.net/renew-license-fcc/, https://rarclub.net/change-address-fcc/
21 Internal Request Error https://law.lis.virginia.gov/vacode/title46.2/chapter8/section46.2-818.2/ no https://rarclub.net/hand-held-law/
For the 405 Method Not Allowed two places link to the same page at the FCC. The link works for me. Here is the code
<ul>
<li>Log in to ULS Online Filing (<a target="_blank" rel="noopener noreferrer"> Link to FCC )</a> with your FCC Registration Number (FRN) and password.</li>The closing ul is after several more li
The second item 21 Internal Request Error is on page https://rarclub.net/hand-held-law/
This last legislature session passed a new version of the state "distracted driver” law (Virginia Code Section 46.2-818.2) that applies to the whole state. The good news is that amateur radio is now exempt from the law. <a >Here is a link to the new law</a>.Again the code works for me.
]]>But when I view page source on the above link nothing shows up (at least when I ctrl + F ‘google’ ]]>
for example they want to search for pants but on the search bar they write “pans” if Relevanssi manages to show the results of pants even if the customer made a mistake to write. ]]>
Zendesk uses Cloudflare DDoS protection and reCAPTCHA, and this results in a “403 forbidden” error when bots scan Zendesk URLs.
Is there a workaround for Google’s reCAPTCHA service, similar to the way that Broken Link Checker can enable successful YouTube link scanning via API, which is also a Google service?
I’m guessing that maybe this is just a known bug with the Broken Link Checker plugin, where it fails with a 403 forbidden error for sites that use Cloudflare DDoS protection and reCAPTCHA, but I’d love to be wrong about this.
Edit: It seems that there’s a related support issue that I didn’t find previously because I searched this support forum for “Zendesk”, and found no matches.
In that forum, Adam (@wpmudev-support8) mentioned that the team was looking into possibly getting whitelisted as a “good bot”, about 1.5 years ago.
That topic closed with a suggestion to whitelist the affected domain, but this doesn’t solve the problem because whitelisting a domain means that the Broken Link Checker plugin will fail to scan the domain for broken links.
]]>