You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/guide/drivers/thunder.md
+80-39Lines changed: 80 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ Thunder Browser：Currently only supports mobile phones (Android, iOS)
51
51
52
52
That is, the mobile phone number, email, and username used for login (there is a probability that you cannot log in, you need to try)
53
53
54
-
-You need to bring the `+86` area code, for example +86 13722223333 fill in like this
54
+
-For phone numbers, try the 11-digit number first. If login fails, try adding the `+86` area code, for example `+86 13722223333`.
55
55
56
56
<br/>
57
57
@@ -65,19 +65,65 @@ password for login
65
65
66
66
67
67
68
-
### **CaptchaToken**
68
+
### **CaptchaToken / CreditKey / DeviceID**
69
+
70
+
`CaptchaToken` usually does not need to be filled manually. If `need verify: {url}` appears when logging in or uploading, open the link in the error and complete the verification. The driver will save the new `CaptchaToken` automatically.
71
+
72
+
`DeviceID` can usually be left empty. The driver will generate and save one automatically. If login verification is triggered, keep the same `DeviceID` before retrying; changing it frequently may make the verification result unusable.
73
+
74
+
`CreditKey` is only used when login verification is triggered. If the following prompt appears when adding the driver, login verification has been triggered:
Need verify: {url} may appear when logging in or uploading, please visit the link in the error to complete the verification and get CaptchaToken (verification code)
Complete the SMS verification. The smart detection page does not need to be completed. It will not redirect back to AList, and clicking the confirm button may not show any prompt.
123
+
124
+
Copy `creditkey` from the console, fill it into the driver's `CreditKey` field, then save the driver configuration.
@@ -113,7 +159,7 @@ Or use the proxy function in this program to transfer.
113
159
### **Login Type**
114
160
115
161
1. When selecting User, you only need to fill in the username and password
116
-
-User You need to bring the `+86` area code, for example +86 13722223333 fill in like this
162
+
-For phone numbers, try the 11-digit number first. If login fails, try adding the `+86` area code, for example `+86 13722223333`.
117
163
118
164
119
165
2.**RefreshToken**: Just fill in RefreshToken when selecting RefreshToken
@@ -124,7 +170,7 @@ Or use the proxy function in this program to transfer.
124
170
125
171
### **Signature Type**
126
172
127
-
**Algorithms**：When selecting Algorithms, just fill in the Algorithms (it is difficult to obtain, and needs to be reversed)
173
+
**Algorithms**: When selecting Algorithms, fill in Algorithms. The default value has been updated to the parameters built into the current driver, so normally keep the default.
128
174
129
175
**Captcha sign**: Only fill in CaptchaSign and Timestamp when selecting CaptchaSign
130
176
@@ -147,53 +193,48 @@ Login type and Sign type recommended options
147
193
148
194
### **DeviceID**
149
195
150
-
The value calculated by md5 is used to determine the logged in device
196
+
Used to identify the login device. If left empty, the driver will generate and save one automatically. If login verification is triggered, keep the same `DeviceID` and retry.
It is related to the signature, fill in according to the actual situation
155
-
156
-
### **UserAgent**
157
-
158
-
UserAgent used by API requests, may be inaccessible or speed limited if the setting is incorrect
159
-
160
-
### **DownUserAgent**
161
-
162
-
The User Agent used for downloading, if the setting is wrong, it will not be downloaded (it will be used when the agent is turned on) Fixed parameters:
163
-
**Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36**
164
-
165
-
<br/>
200
+
These values are related to signing and login. The defaults have been updated to:
166
201
202
+
-`ClientID`: `Xp6vsxz_7IYVw2BB`
203
+
-`ClientSecret`: `Xp6vsy4tN9toTVdMSpomVdXpRmES`
204
+
-`ClientVersion`: `8.31.0.9726`
205
+
-`PackageName`: `com.xunlei.downloadprovider`
167
206
207
+
Normally keep the defaults.
168
208
169
-
## **Key data acquisition process**
209
+
###**UserAgent**
170
210
171
-
Obtain Xunlei request data through network analysis tools (packet capture tools) --- Please read the following information carefully
211
+
UserAgent used by API requests. Incorrect values may cause access failure or speed limits. The default has been updated to `ANDROID-com.xunlei.downloadprovider/8.31.0.9726 ... sdkVersion/512000 ...`.
172
212
173
-
Open Xunlei and log in to your account (the picture below uses the PC client to operate, and the web terminal is also available)
213
+
### **DownUserAgent**
174
214
175
-
Included in the request https://xluser-ssl.xunlei.com/v1/shield/captcha/init
After logging in to Thunder and opening the packet capture tool, it is possible that the information of **v1/shield/captcha/init** cannot be immediately obtained at this time.
219
+
### **CreditKey**
181
220
182
-
Do not close the Xunlei PC client and the packet capture tool, just wait, it will refresh automatically after **5 minutes**
221
+
Only used when login verification is triggered. Use the same handling steps as [CaptchaToken / CreditKey / DeviceID](#captchatoken--creditkey--deviceid). After a successful login, the driver clears this field.
183
222
184
-
You will see the parameters as shown in the figure below, and you can fill in it according to the acquisition (if you can't see it clearly, you can right-click to copy the picture and link it to the browser to open a new window)
223
+
<br/>
185
224
186
-
See **v1/shield/captcha/init** and grab it, please **immediately don't delay for a second** Right-click Xunlei in the taskbar in the lower right corner to exit, exit completely and then reopen to get * *Figure II**
187
225
188
-
189
226
190
-
Restarting Thunder will refresh the token
227
+
## **Key data acquisition process**
191
228
192
-
The request to https://xluser-ssl.xunlei.com/v1/auth/token contains RefreshToken (please use the returned value), ClientSecret (does not exist on the web side)
229
+
After PR [#8342](https://github.com/AlistGo/alist/pull/8342), username/password login for `Thunder` and `ThunderExpert` was changed:
193
230
194
-
231
+
1. The driver first calls `https://xluser-ssl.xunlei.com/xluser.core.login/v3/login` to get `sessionID`.
232
+
2. It then calls `https://xluser-ssl.xunlei.com/v1/auth/signin/token` to exchange the token used by AList.
233
+
3. Login parameters were updated to Xunlei Android client `8.31.0.9726` and `sdkVersion/512000`.
234
+
4. A `CreditKey` field was added for login verification.
235
+
5. The normal `Thunder` driver can also customize `DeviceID`.
195
236
196
-
Figure 1 contains **7** parameters | Figure 1 contains **2** parameters | a fixed parameter (Down UserAgent), ten parameters and 3 options and a mount path, just write and save, before saving Remember to check~
237
+
Therefore, the old process of capturing `v1/shield/captcha/init` and `v1/auth/token` to obtain `CaptchaSign`, `Timestamp`, `RefreshToken`, and related fields is outdated. Prefer the normal `Thunder` driver and only fill in username and password. Use `ThunderExpert` only when advanced parameters or custom UserAgent are needed.
0 commit comments