Feedback: The KEY on youku cannot be obtained

[hjkow]

Google translated

I used Google Chrome and Firefox browsers respectively, and when the extension was running, I selected Youku, but after clicking Result, the cursor was always in a circle state. KEY cannot appear. I hope the author can fix it. Thank you very much!

Original comment

我分别使用了Google Chrome和Firefox浏览器，并在扩展运行时，选择了Youku，但是点击Result后，光标一直是圆圈状态。无法出现KEY，希望作者能够修复一下，万分感谢！

[FoxRefire]

Logs?

1.Logs from Guesser window 2.Logs from Video window 3.HAR from Video window after extension executed

[FoxRefire]

Closed due to inactivity The issue will reopened when activity occurs.

[hjkow]

日志？

1.来自猜测窗口的日志 2.来自视频窗口的日志 3.执行扩展后来自视频窗口的 HAR

Can you help me take a look

[FoxRefire]

Go to the Network tab and check and let me know the response of the request made by the extension

[hjkow]

Go to the Network tab and check and let me know the response of the request made by the extension

As shown in the above figure, Youku cannot obtain it

[FoxRefire]

Need response body of failed request

[hjkow]

请求失败的响应体

There is no abnormal response subject, but the key cannot be obtained, which feels a bit stuck

[FoxRefire]

Then, open python/schemes/Youku.py and insert line print("DEBUG:"+res) after line 8 of the file. And could you send console log of Guesser window, not video window.

[hjkow]

然后，打开文件python/schemes/Youku.py并在第 8 行之后插入行print("DEBUG:"+res)。 您能否发送 Guesser 窗口的控制台日志，而不是视频窗口。

[dreammu]

Need response body of failed request

Basically "invalid argument" in Chinese

browser request wvg request

It looks like wvg's request incorrectly adds [' and ']

[FoxRefire]

Closed in #24

[dreammu]

I'm requesting to reopen this issue, this is different from the situation I mentioned before. His situation is sending a request but not receiving a response, which I also encountered but I can't reproduce it stably.

[FoxRefire]

I also encountered but I can't reproduce it stably.

@dreammu @hjkow Is this problem still occurring? The random problems that have been occurring since fix #24 were probably caused by corsFetch, which has already been fixed. If the issue is still persisting, I will keep the issue open, but if we are sure the issue is no longer occurring or there is no response, I will close the issue.