One request path returns 403

Hello

I'm writing here because one of my endpoints started returning 403 today.

I know it is not recommended, but I'm using Cloudflare as reverse proxy (to decrease edge requests).

I'm hosting an addon, for which it is normal that one specific endpoint is queried all the time. But probably because of Cloudflare, for the system it looked like one address queried the same addressal the time and this probably triggered some kind of protection. And now all requests to it return 403, even though all other endpoints work fine.

I tried to bypass this with a custom firewall rule but it did not help.

Is there anything I can do to fix this, without resigning from Cloudflare?

After disabling Tiered Cache, everything started to work again. Is it possible to have Tiered Cache enabled with Vercel?

Vercel Staff

From the product page, Cloudflare will insist on caching more often, for each/more data centers → https://developers.cloudflare.com/cache/how-to/tiered-cache/

Thus, how and why this is done is perhaps a better question for the Cloudflare team.

I am glad that you were able to identify this, and we appreciate you feeding back to us!

Well, I know how Tiered Cache works and what it does. My question was, it is possible to use it with Vercel, or will it always mark it as "suspicious" and later block specific request paths with 403 error

This topic is closed. It no longer accepts new replies.