token itself is used for encryption. The backend returns the token to you, and you get the token stitching. Other people know that token can't understand what that string is.


fetch/xmlhttprequest turn to blob to regenerate into a local attachment link to download.


how was the problem of landlord finally solved? now I also encounter the same problem


if it's token, you've already got it on the page.
then you go straight (as follows)

<a href='wwww.xxxxx.com/?token=asdczlkxcjklfjsdk'>

just splice it.

if it becomes random, you can use token as a variable and bind it to the a tag, which can be changed at any time.

normally, this is a get request. If you make a request like this directly, your backend can take out the parameters in the url and process them to determine whether you should download

.

Js dynamically acquires token, and dynamically splices

when clicking .
Menu