-
Notifications
You must be signed in to change notification settings - Fork 357
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
亲,检测到您的访问异常,请重新试试吧~ #128
Comments
应该不是账号被检测了,可能是太快的进入抢票,导致被检测到,给你拦截了。可以试试修正时间往后延迟个1、2秒试试呢。这个需要更多的测试和反馈才能知道是怎么回事。 |
好的👌
shiyu ***@***.***>于2024年5月12日 周日10:52写道:
…
应该不是账号被检测了,可能是太快的进入抢票,导致被检测到,给你拦截了。可以试试修正时间往后延迟个1、2秒试试呢。这个需要更多的测试和反馈才能知道是怎么回事。
—
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUJTVLAR2GLLNTFMHWU3NSLZB3KNRAVCNFSM6AAAAABHR23342VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGA4TQMBZGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
在倒计时结束再次调用获取商品的函数就可以获取到signkey了。就不会有异常了。只不过和手抢没啥区别了。这个t只会在商品倒计时结束后再给你。已经可以购买的商品可以拿的到。预售商品拿不到t |
除非了解这个t是怎么生成的,自己加密生成,然后再创建订单,提交订单。这样可以省一步获取商品信息的请求。似乎是base64编码 |
这个怎么解决啊 是号被检测了还是啥
The text was updated successfully, but these errors were encountered: