Warning Code: 0 cURL error XX

I tried visiting these URLs with a browser with spoofed user agent WordPress/6.6.2; https://example.com and found that the URLs with error code 52 and 56 did indeed fail. So these reported responses seem logical. Apparently some servers freak out when the word WordPress appears in the user agent header… Any chance to make the user agent an option?

The other two, I cannot figure out why these would turn up as Warning.

The saint-vincent-de-durfort.fr server responds with a regular valid Let’s Encrypt license and lannuaire.service-public.fr/auvergne-rhone-alpes/ardeche/56e5401a-605e-4c3a-8d97-1f9dba7e787f never responds slow to my browser requests, no matter what I try…

Even though there is a valid certificate, there are issues with it. You can see see them when running an SSL scan here: https://www.ssllabs.com/ssltest/analyze.html?d=www.saint-vincent-de-durfort.fr

Timeouts, even if they last forever, will always just time out and return an error code 0 when it gives up. If you want code 0 to return as broken rather than a warning, you can hook into the blnotifier_bad_status_codes filter and add 0 to it, and the blnotifier_warning_status_codes filter to remove 0 from it. Let me know if you need help implementing those.

And yes I can add a user agent field for you. ??

Please update to version 1.1.4.

I added the field for user agent, as well as an option for marking the status code 0 as broken instead of a warning. This way you don’t have to hook into them. Hope that helps.

Amazing! Replacing “WordPress” in the user agent field solved many of the Warnings…

The only false positives remaining are the ones with “cUrl error 28” for URLs like https://lannuaire.service-public.fr/auvergne-rhone-alpes/ardeche/e127fd74-cb4a-4a97-ab90-3b01591e2717 … Visiting these in a normal browser shows no issues, no redirects, no timeouts.

I’ve even tried the most common user agent (Chrome on Windows) but the timeouts in Broken Link Notifier remain. HEAD or GET method, no difference. Any idea why that would be going wrong here?

• This reply was modified 2 months, 2 weeks ago by Rolf Allard van Hagen.

Could be that their server is blocking requests with a firewall or is just slow to respond. Maybe outdated cURL or some kind of conflict with their website. If you know it’s working, I would just omit it at this point.

… I would just omit it at this point.

That seems the only solution… It’s a pity because URLs on that directory site tend to change sometimes :/

In any case, is there a way to exclude a complete site domain (or parent path) to ignore instead of each individual link to that site?

Yes, you can go to Broken Link Notifier > Omitted Links, and then include the domain with a wild-card (asterisk), for example: https://example.com/*. This will omit everything that starts with that domain.

Excellent stuff!