The crawler should right-click to view the source code of the webpage > View the source code of the webpage. Instead of in the review element, the code seen here has been rendered by js, which is different from the original code, and the code obtained by the crawler has not been through js Rendered, that is, the original code. I took a look and found that the Thunder download address was calculated using js The specific code is as follows:
function ThunderEncode(t_url) {
var thunderPrefix = "AA";
var thunderPosix = "ZZ";
var thunderTitle = "thunder://";
var thunderUrl = thunderTitle + base64encode(utf16to8(thunderPrefix + t_url + thunderPosix));
return thunderUrl;
}
Tested it: Pass the address ftp://a:a@dygod18.com:21/[电影天堂www.dy2018.com]忍者神龟2破影而出BD中英双字.rmvb as a parameter and you will get a Thunder connection, but it is different from the one on the web page. After recoding, it URL-encodes the Chinese characters. As long as the encoding is unified, there will be no problem. .
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The crawler should right-click to view the source code of the webpage > View the source code of the webpage. Instead of in the review element, the code seen here has been rendered by js, which is different from the original code, and the code obtained by the crawler has not been through js Rendered, that is, the original code.
I took a look and found that the Thunder download address was calculated using js
The specific code is as follows:
Tested it:
Pass the address
ftp://a:a@dygod18.com:21/[电影天堂www.dy2018.com]忍者神龟2破影而出BD中英双字.rmvbas a parameter and you will get a Thunder connection, but it is different from the one on the web page. After recoding, it URL-encodes the Chinese characters. As long as the encoding is unified, there will be no problem. .