ivory kestrel
Accessing a url that returns an X-FRAME-OPTIONS header or some other policy prevents cloudflare/puppateer from loading that page. I am trying to build a workers api that takes a screenshot, and it does work for some urls, but it does not work for other sites. The screenshot renders an error (see screenshot attached).
Would it be possible to use some kind of plugin to bypass those policies and render the page in cloudflare workers?
bleak nest
Have you considered the fact that shopify is using cloudflare to block bots which includes browser rendering?
ivory kestrel
It looks like it, but the same system backfires and treats the puppateer instance within workers as a bot? Is there a way to bypass that?
bleak nest
It doesn’t backfire, that’s intended behaviour
ivory kestrel
I understand that, so there is no way to actually take screenshots of those sites that use some kind of bot protection, correct?
bleak nest
Yep
ivory kestrel
I actually tried a pure nodeJs project (instead of wrangler) and it all worked as expected. It looks like the environment where workers are executed is treated as potentially unsafe. Not sure how that works behind the scenes (I assume some certificate or header might be involved, or purely an IP blacklist), but moving away from CF Workers fixes this issue, for anyone interested.
quasi musk
Hello guys, well.. I know it has nothing to do with the subject you were talking about, but could you help me with a website?
I tried to talk to the owner of the site but you blocked me
well for now I'll explain I was watching anime on the website goanimes.net until I went to the next episode until it appeared that I was blocked and I should send an email to the website developer but every time I do I get blocked again