Some internet sites block Headless Chrome, here’s ways to get around it.
Troubleshooting is type in all aspects of computer systems and development — this article begins with simple tips to figure this nagging issue out all on your own. In the event that you don’t care, jump towards the TL;DR by the end.
If you’re having difficulty with headless mode, make sure to have a screenshot with page.screenshot() so that you can see what’s happening. At least it tells you you have with headed mode and you’re not stuck at a broken script without understanding what you’re working with if you’re dealing with the same visible content.
In this instance the server didn’t also react because of the appropriate web site it self. The initial response is an “Access Denied” page and that’s all we can get whenever operating Chrome in headless mode. This does not take place at all in headed mode.
When troubleshooting it’s crucial to recognize everything we understand and that which we don’t understand. Without this action it is impractical to pursue a program of action that targets the unknown and it is redundant that is n’t. This might appear fundamental but, until you understand just why, it is non-intuitive how to get there. Troubleshooting might be viewed as running all the way through a list but that only works for those who have experienced the issue prior to.
Exactly exactly What do we realize? We understand that the web web browser produced solitary demand and we received a reply that currently stated access denied. The initial web page wasn’t rendered and also the web web browser made hardly any other needs. This means a host someplace produced call based strictly about what we delivered for that very first demand and our block has nothing in connection with page content. That guidelines out troubleshooting any such thing following the web web page render and limits our scope into the demand alone. The demand it self is a lot of bits and bytes delivered on the internet and accepted by a server.