So I installed and pulled this docker on a local Synology to check if it was an IP thing. Testing it again with my NAS parser I got the error -> "Resource returned a response status code of 200 and resource was instructed to reject non-200 status codes."?
Current Mercury Parser Version
Node Version 13.14.0
Synology NAS / Docker
I presume the 403 is to be expected and common on some sites? Not experimented with the user-agent or anything else as to knowing what exactly causes it... though I am a bit curious to the error message I got on the NAS, thinking it would work better if on a residential IP.
Being more curious than anything... while it seems the parser fails on this domain generally (received a 403 on a cloud hosted mercury parser). https://www.pcgameshardware.de/GTA-5-Grand-Theft-Auto-5-Spiel-4795/Specials/GTA-5-Benchmarks-1261429/
So I installed and pulled this docker on a local Synology to check if it was an IP thing. Testing it again with my NAS parser I got the error -> "Resource returned a response status code of 200 and resource was instructed to reject non-200 status codes."?
Current Mercury Parser Version Node Version 13.14.0 Synology NAS / Docker
I presume the 403 is to be expected and common on some sites? Not experimented with the user-agent or anything else as to knowing what exactly causes it... though I am a bit curious to the error message I got on the NAS, thinking it would work better if on a residential IP.