m1saka
7d8a5b6f74
The 1.4.2 extension replaced the old signed/encrypted chat gateway with an
OpenAI-compatible aigateway. Align the proxy with the new flow:
- Use ecloud.10086.cn login/model base URLs, zhanlu_ide plugin headers and
v1.4.2 plugin version
- Provision the model API key via SM2-signed get-or-create after v1/login
profile fetch; store api_key/model_base_url/email in credentials
- Chat via Bearer apiKey against {modelBaseUrl}/chat/completions with plain
OpenAI SSE passthrough; fetch /v1/models from the gateway model-info endpoint
- Force HTTP/1.1 upstream (gateway drops HTTP/2 ALPN negotiation with EOF)
- Drop obsolete AES body encryption, model name mapping and vscode headers
11 lines
85 B
Plaintext
11 lines
85 B
Plaintext
credentials.json
|
|
extension/
|
|
*.exe
|
|
*.log
|
|
.env
|
|
.env.*
|
|
!.env.example
|
|
tmp/
|
|
temp/
|
|
source/
|