Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
rtve.es:alacarta not working. Unable to download webpage. #5011
Comments
helq
commented
Feb 20, 2015
|
Hi, thank you for your incredible software! And sorry for only coming here to post about the support of one uninteresting page. ^^ |
|
I've partially fixed the extraction in yan12125/youtube-dl@24523c5. Seems rtve.es has totally changed how stuff works, so I rewrote rtve.py. I didn't issue a pull request primarily because in my codes Pycrypto is used for Blowfish encryption and decryption. If someone can provide a Blowfish implementation that:
I'll issue a pull request to merge my changes. It's also possible to use the |
|
For a few videos I have tested (the current tests and some from http://www.rtve.es/documentales/), the current method works. |
|
Yes - I implement the algorithm based on the flash player. If someone can provide a Blowfish implementation, I think it will be great to merge the two approaches. |
|
I've checked out how Android Apps works and seems they're using AES now. The good news is that I can integrate the algorithm into youtube-dl. See yan12125/youtube-dl@0eede00. The bad news is that videos got on Android is smaller. For exmaple, for http://www.rtve.es/alacarta/videos/el-ministerio-del-tiempo/emdt-6-280315/3066559/, I got a 1024x576, 772.31MiB file using the BlowFish version, and got a 640x368, 379.41MiB file with the AES version. |
|
@jaimeMF Which video are you testing? By the way, upon commit e9f65f8, I've tested several UA strings for the video proposed by @helq (with
While some gives me a 404 error:
Note that in successful cases, the downloaded file is smaller and have lower resolutions in comparison with the file downloaded with my fork. I guess the reason is that the current algorithm is based on the mobile app, so some videos cannot be fetched unless you claim you're using a mobile device. Nevertheless, changing user agent strings is a reasonable workaround. |