[R-pkg-devel] DOI in Description (possibly) invalid

[Murray Efford]

Ivan
Thanks for your detailed explanation that I'm sure will be useful to others as well. We can hope unnecessary obstacles like this become rarer; the reverse seems true.
Murray

________________________________________
From: Ivan Krylov <krylov.r00t using gmail.com>
Sent: 08 May 2022 23:29
To: Murray Efford
Cc: R-package-devel using r-project.org
Subject: Re: [R-pkg-devel] DOI in Description (possibly) invalid

On Sun, 8 May 2022 08:01:16 +0000
Murray Efford <murray.efford using otago.ac.nz> wrote:

> This results in checks reporting "Found the following (possibly)
> invalid DOIs:... Service unavailable".

This happens because there's Cloudflare sitting between the world and
Wiley Online Library, and Cloudflare replies with the HTTP error code
503 to requests it doesn't like. When checking DOIs for validity, R CMD
check doesn't bother pretending to be a human operating a browser (it's
hard and keeps getting harder), so Cloudflare classifies this request
as automated and possibly malicious and refuses to serve it. On the
other hand, when you follow the link manually with a browser,
Cloudflare knows you're a human because it's been keeping track of your
browsing patterns across other websites under Cloudflare protection,
and they match typical human behaviour, so you get the content.

It's a known problem. For now, you just have to mention it in the
submission comment.

There has been a suggestion to change the DOI check so that it would
stop after one request to the https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoi.org%2F&data=05%7C01%7Cmurray.efford%40otago.ac.nz%7C1e9f974f75ef4c6c952908da30e60702%7C0225efc578fe4928b1579ef24809e9ba%7C0%7C0%7C637876061769983877%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2Y3FHbOqe0Hdz620FcT3oXmg5zBHHf7fZxJLgyu3XjE%3D&reserved=0 server (which doesn't
discriminate against such automated requests for now) and doesn't try
to follow the link returned by doi.org (which might). Perhaps it would
get implemented when this problem gets worse.

--
Best regards,
Ivan