-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always 403 when trying to download the actual video segments in m3u8 #12
Comments
Can you provide details information to here? Because I tested downloading the recent video via Most the reasons of 403 are caused by network proxy and resource expired. |
Avgle actually gives an "invalid/unusable" m3u8 file when it thinks you didn't solve the captcha. As far as I remember this was a lot more common with one of their file-hosting backends. To add a bit to how Avgle works. When you visit the page from a non-validated IP (one that hasn't solved the CAPTCHA recently) the flow is like this
The video URL is, as far a I remember, not actually restricted to a specific IP, although it might matter how far into the rabbithole you travel before you decide on which URL to use. |
But Captcha sometimes isn't shown at all but videos get played.
I guess the issue is that we log the invalid video first but doesn't update it when the next valid URL comes up? |
I'm sure there is no proxy at all, and |
Isn't scraping avgle fun?!
Not sure how the project does exactly. Looking through the code and readme I saw no mention or checks for the captcha. |
Always 403 when trying to download the actual video segments through the address in .m3u8 file which was downloaded with the "Avgledownloader" with idm. by the way: However,when I copied the address of .ts file sniffed by IDM extension in Chrome, then put it to "Add URL" to download it, idm went to error with code 403? In chrome->network, I could find the .ts file and "save as " it. At first I thought the difference between the two ways was "user-agent", I updated the version of idm to 6.35 and added a user-agent string, it doesn't work either. So, the url is something like "http://xxxx.com/key=lagjlasjdgl=/media=hlsA/xxxx.mp4/seg-001.ts" 欸欸,发布者可以读懂中文的。那我就中文再说一下,就是通过这个问题顺便搞清楚下,怎么回事。 比较想搞清楚的是,通过嗅探下载,和直接添加地址下载,有什么区别。你的这个程序里面,为什么却能够下载成功,看log文件,也发现了很多个403了。很好奇这个,到底为什么我不行。 |
@freeleefly 其实这个很玄幻, 有可能式 |
谢谢你,发现了,好像确实是 referer的问题。 |
啊,还有一个问题。我在页面上,看到视频地址是被blob加密的,请问,这个你是怎么通过这个blob的地址找到m3u8地址的呢? |
@freeleefly 哪个视频是被加密的,我目前遇到的只有 base64 编码过的。如果你真的遇到有加密的,可以参考一下这个仓库:https://github.com/video-dev/hls.js/#supported-m3u8-tags |
不不不,就是从html可以看到 这里。 |
@freeleefly 我没有知道你的意思,你是说怎么从一个 URL 获取到 m3u8 的链接的吗? |
对的,因为src的属性是 blob:http....,对这样一段,不知道怎么处理能够得到m3u8,想知道这个。 |
The m3u8 file is correctly downloaded and decoded, but none of the segments are accessible. I've ruled out any proxies or ambiguous routes, and tried ffmpeg to download the m3u8 directly. However it still yields 403. I guess avgle site updated again?
The text was updated successfully, but these errors were encountered: