WordPress / openverse

Openverse is a search engine for openly-licensed media. This monorepo includes all application code.
https://openverse.org
MIT License
233 stars 183 forks source link

AxiosError: Request failed with status code 403 #4630

Open sentry-io[bot] opened 1 month ago

sentry-io[bot] commented 1 month ago

Sentry Issue: OPENVERSE-FRONTEND-1YN

AxiosError: Request failed with status code 403
  at None (/_nuxt/2025b13.modern.js:2:267107)
  at XMLHttpRequest.w (/_nuxt/2025b13.modern.js:2:267258)
AetherUnbound commented 1 month ago

More context on this issue: we've had 851 instance of it arise in the last 30 days, and it first started showing up on July 5th (our last deployment prior to that was https://docs.openverse.org/changelogs/frontend/2024.07.01.20.35.48.html). Most of the requests originated from our homepage, and 83% of them originated from the "Yeti" browser, although the rest did not. This seems like something we should look into, though I'm not sure how to find in Sentry which URL was causing the 403.

zackkrida commented 1 month ago

@AetherUnbound Yeti, the crawler used by Naver (South Korea’s main search engine), is getting 403s when they're on the frontend and the /stats endpoints are requested.

They're being blocked by one of our Managed challenge rules from the API, but not the frontend, which causes the errors. I'm not certain how we're blocking them on one service and not the other.