8000 Expected HTTP 101 response but was '200 OK' · Issue #14 · cssxsh/mirai-new-bing · GitHub 8000
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Expected HTTP 101 response but was '200 OK' #14
Closed
@dokurorz

Description

@dokurorz

已经使用相同IP重新登录获取cookies,插件配置中的代理为空,测试过IP可以网页正常使用newbing
mirai和插件版本如下

 10:53:28 [INFO] Verifying "net.mamoe:mirai-console" v2.15.0
  10:53:29 [INFO] Verifying "net.mamoe:mirai-console-terminal"
 v2.15.0
  10:53:30 [INFO] Verifying "net.mamoe:mirai-core-all" v2.15.0
  10:53:31 [INFO] Verifying "org.itxtech:mcl-addon" v2.1.1
  10:53:31 [INFO] Verifying "net.mamoe:mirai-api-http" v2.9.1
  10:53:32 [INFO] Verifying "net.mamoe:chat-command" v0.6.0
  10:53:32 [INFO] Verifying "xyz.cssxsh.mirai:mirai-new-bing"
v0.4.3
  10:53:32 [INFO] Verifying "xyz.cssxsh.mirai:mirai-openai-plu
gin" v1.5.1
  10:53:33 [INFO] Verifying "xyz.cssxsh:bilibili-helper" v1.7.3

报错如下

2023-07-13 10:42:56 W/MiraiNewBingListener: MiraiNewBingListen
er with 全 局 代 理
java.net.ProtocolException: Expected HTTP 101 response but was
 '200 OK'
        at mirai-new-bing-0.4.3.mirai2.jar[private]//okhttp3.i
nternal.ws.RealWebSocket.checkUpgradeSuccess$okhttp(RealWebSoc
ket.kt:224)
        at mirai-new-bing-0.4.3.mirai2.jar[private]//okhttp3.i
nternal.ws.RealWebSocket$connect$1.onResponse(RealWebSocket.kt
:170)
        at mirai-new-bing-0.4.3.mirai2.jar[private]//okhttp3.i
nternal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
        at java.base/java.util.concurrent.ThreadPoolExecutor.r
unWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$W
orker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:829)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

Status

👌

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0