Talk about the anti-climbing mechanism in the Himalayas?

recently I want to do big data analysis, so I want to crawl all the user information in Himalayas.
then the key point is, I found that there is a single-module defense mechanism in Himalayas. For example, when I crawled about 2000 + on a personal user"s home page, the anti-crawling mechanism took effect. No matter which user"s home page I visited, I returned 503, and even my own personal center could not log in.
I"ve tried cookie transformations, but I"ve come to the conclusion that IP is definitely banned. I would like to ask you, do you have any relevant experience? Whether IP is banned or not.

Dec.09,2021

climb with mobile traffic


Himalayas are double sealed, first write the blocked field in your cookies, and then block IP;
if you change the IP, you will die if you don't clean up the cookies,. So the way to unseal it is to clean up the cookie, first and then change the IP. Then visit OK.


I am an agent IP. Some clients have set up an anti-crawling department to study how to bypass risk control and grab data. It is suggested that everyone try this method

.
MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1ea6687-47ba7.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1ea6687-47ba7.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?