Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Receive 403 from working URL #46

Closed
danielinteractive opened this issue Sep 20, 2024 · 2 comments
Closed

Receive 403 from working URL #46

danielinteractive opened this issue Sep 20, 2024 · 2 comments

Comments

@danielinteractive
Copy link

Hello @gaborcsardi,

maybe a naive question, but I am not sure why I receive "403: Forbidden" from checking
https://doi.org/10.1002%2f%28SICI%291097-0258%2819971030%2916%3a20%3c2349%3a%3aAID-SIM667%3e3.0.CO%3b2-E
is it because Wiley has some kind of check for non-human access or so?

If that is the case, is there an option to "whitelist" this for urlchecker usage?

Thanks a lot,
cheers
Daniel

> urlchecker::url_check()
Loading required namespace: mmrmError: README.md:25:9 403: Forbidden
(1997)](https://doi.org/10.1002%2f%28SICI%291097-0258%2819971030%2916%3a20%3c2349%3a%3aAID-SIM667%3e3.0.CO%3b2-E)
@gaborcsardi
Copy link
Member

is it because Wiley has some kind of check for non-human access or so?

I think so:

❯ curl -s -L --head 'https://doi.org/10.1002%2f%28SICI%291097-0258%2819971030%2916%3a20%3c2349%3a%3aAID-SIM667%3e3.0.CO%3b2-E' | grep ^HTTP
HTTP/2 302
HTTP/2 403

If that is the case, is there an option to "whitelist" this for urlchecker usage?

Maybe: #45.

@danielinteractive
Copy link
Author

OK I guess this is duplicate from #45 then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants