”unauthorized request" and "chathub not authorized".

[chinazhaoht]

I used the signature in the X-Sydney-Encryptedconversationsignature header from the create conversation response, URL-encoded it, and passed it as the sec_access_token to the chathub interface, but the chathub still returns "unauthorized request" and "chathub not authorized".

[nikilagar]

Due to recent bing API update, we might need to pass more cookies. Please refer to https://github.com/transitive-bullshit/bing-chat/pull/56/files/a4cd8089432ac75b15eb51b25a8f1154cac8d0f3#diff-eb0f70fdf73c5fc4372815575d2b38fd700baf4b9abe1b67738771563a70ce70 for complete solution.

[typoworx-de]

Thanks for the hint @nikilagar. Well I'm not a pro in nodejs, but I think this is a good starting point:
https://github.com/tuhinpal/bingchat-api/pull/12/files

[typoworx-de]

Good news by fiddling around trying to port the idea of catching the security-token from response (thanks forr @nikilagar for the hint) I've got it working locally and provided the patch (see link above) and provided a pull-request.

I've got a live-sign of GPT :-D