[Feature] 部署在vercel上GOOGLE_API_KEY失效的问题，希望修改获取KEY的代码部分

[KevinBrk]

使用中发现在vercel上设置了GOOGLE_API_KEY无效

看源代码后发现，在api/google/route.ts文件第52行直接获取头部Authorization的值，有值直接使用无值才会使用服务端配置

但是当配置访问密码CODE后，头部Authorization是一直都有nk-xxxxxxx这样格式的值导致判断错误

希望能修复这个问题，感谢！

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

Title: [Feature] The problem of GOOGLE_API_KEY failure when deployed on vercel. I hope to modify the code part for obtaining KEY.

During use, it was found that the GOOGLE_API_KEY set on vercel was invalid.

After looking at the source code, I found that in line 52 of the [api/google/route.ts file](https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/981a3629b6eeb9f41090c2a7cd4fd568f6981a55/app/api/google/%5B. ..path%5D/route.ts#L52) Directly obtain the value of the header Authorization. If there is a value, use it directly. If there is no value, the server configuration will be used.

However, after configuring the access password CODE, the Authorization header always has a value in the format of nk-xxxxxxx, which leads to incorrect judgment.

Hope this can be fixed, thanks!

[RoversX]

使用中发现在vercel上设置了GOOGLE_API_KEY无效

看源代码后发现，在api/google/route.ts文件第52行直接获取头部Authorization的值，有值直接使用无值才会使用服务端配置

但是当配置访问密码CODE后，头部Authorization是一直都有nk-xxxxxxx这样格式的值导致判断错误

希望能修复这个问题，感谢！

Same problem

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically.

---

During use, it was found that the GOOGLE_API_KEY set on vercel was invalid.

After looking at the source code, I found that in line 52 of the [api/google/route.ts file](https://github.com/ChatGPTNextWeb/ChatGPT-Next-Web/blob/981a3629b6eeb9f41090c2a7cd4fd568f6981a55/app/api/google/%5B ...path%5D/route.ts#L52) directly obtains the value of the header Authorization. If there is a value, use it directly. If there is no value, the server configuration will be used.

But when the access password CODE is configured, the Authorization header always has a value in the format of nk-xxxxxxx, which leads to an error in judgment.

Hope this can be fixed, thanks!

Same problem

[fred-bf]

Hi, the authorization key were injected through(a bit hacky)

ChatGPT-Next-Web/app/api/auth.ts

Line 68 in 981a362

req.headers.set("Authorization", `Bearer ${systemApiKey}`);

I tried to reproduce the issue, but it works fine on my end. if you still encounter please provide a reproducible environment or provide env keys you've set.