ChatGPTNextWeb / ChatGPTNextWeb/NextChat
[Feature] configurable **client** certificate
- Dominant language
- TypeScript
- Stars
- 88.8k
- Forks
- 59.1k
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I encountered a problem with the client certificate verifying / authenticating.
When enabled client certs (typically the Cloudflare mTLS rules), the client must present its private cert (aka .p12/.pfx file) to the server. However since `ChatGPT-Next-Web` requests the API base from the backend, it would not carry the valid credentials that should have come from a browser request.
So there should be a configurable option to specify a client certificate so that the mutual verification would work.
I have read the issue list and found that #518 #3034 may be related, but both of them didn't mention if it's possible to deploy a **client certificate** for the backend.
My current approach is to allow the server IP as _request src_ip_, but it's quite inconvenient since I had to hard code the IP into the rules. So let me ask for a feature to satisfy this scene.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.