Thanks to everyone for the extra information requested by cloudflare tech support
What we need to do now is to try and replicate the issue through making direct requests to image.tmdb.org - when we tried making individual requests before through curl, they did not fail - the issue may be only arising when a batch of requests are made
I have been looking replicating what was seen in the wireshark capture provided by @gonse and to produce a windows batch file that makes similar requests as was in the wireshark capture and to capture the results
@gonse If you are available to help, I have a windows batch file that will make 84 image fetches batched in similar way to what I saw in the wireshark and then we can see if any fail. I am adding similar delays between the batches of requests as was observed
I will send you zip of the batch file in a private message. Please create a directory where you place that batch file in and also copy curl.exe to the same directory
Then in a command line window, run the batch file. It will spawn a number of command line sessions for the requests made in parallel and will then suspend for a number of seconds before firing off another batch and so on until all 84 requests are made. The image files fetched will be stored in that directory as well as the response headers received for reach request
At the end please zip the directory and send it to me
Thanks
