@SynergeticWebSolutions said:

@sctsnipe said: I suddenly won't get any response from the CDN for images, and all connections will time out. If I hop on a VPN, everything starts working as expected. I understanding wanting to protect against DDOS attacks, but I should be far from triggering a block like this, I imagine?

Interesting...found the opposite to be true (disabling VPN fixes the problem). Wondering if it's the ISP/VPN that makes the difference? Also, sometimes the tmdb.org vs themoviedb.org domains will alternatively work (find an image URL provided on this website vs the API's configuration URL), but that's probably not recommended switching for the sake of TMDB's primary servers. Either way, it's doubtful this is something that is within @travisbell 's (no pun intended) domain to fix. This is likely something automatically determined by the CDN.

I mean, if the issue is that the CDN they are using is aggressively banning users from accessing images on their CDN, then it's something the TMDB folks can fix but adjusting how strict their DDoS protection is. I do not see others with this problem who use my application (or at least no major reports of it yet), so I wonder if the "AI" behind their CDN (looks like they use Bunny CDN) is banning me more aggressively because I have an Asian IP address (Japan)? I have already implemented systems to rate limit API requests within the thresholds mentioned above. Still, I am just accessing CDN images directly through the browser, and it was enough for me to get blocked.

Either way, still fully banned from accessing image.tmdb.org. Travis, there has gotta be something you can do here. I can't develop my application anymore without using a VPN and that's just not going to work long term.

Hey guys, as I noticed this is fixed finally. I am making 3 calls simultaneously and showing around 60 images on a single page without a problem. Can someone else confirm this? Cheers @sctsnipe @SynergeticWebSolutions

@backA05 said:

Hey guys, as I noticed this is fixed finally. I am making 3 calls simultaneously and showing around 60 images on a single page without a problem. Can someone else confirm this? Cheers @sctsnipe @SynergeticWebSolutions

I noticed that I have started getting Cloudfront as the CDN for some of the images now instead of Bunny CDN. But as of my last test a few days ago, Bunny CDN responses were still in there. Maybe an A/B test? I have built much more aggressive image caching in the meantime which is helping as well. Some confirmation from the devs here would be very helpful.

@travisbell said:

One of our CDN providers enforces some base level rate limiting to help prevent DDOS attacks. I believe it's a maximum of 50 requests per second and 20 connections per IP.

this has confused me a bit, if i have set of 100 ids i want to search (essentially needing to make 100 requests) i know your 50 rate limit means i can only make up to 50 calls per second, but when you say 20 connections per IP i dont understand this, does it mean that if have an array with 100 ids, for every request that i make, that counts as an open connection until the response is received? therefore meaning i can only have 20 of those open connections at any given time per IP?

@travisbell any chance to configure the CDN to show some headers regarding the rate limit (remaining requests or timeout time once limit reached)? Right now it seems like a blackbox, where users need to do guesswork in order to avoid the limit

Unfortunately, no, it is not possible.