Yes login is working well without bypassing
but when I start chat, error message occurred
I found some documents, that is indicate chatgpt make API token. I guess F5 can't make API connection because of token
Has this problem been resolved?
I am experiencing the same problem in my environment.
Logging in is fine, but when I first send the chat, I get an error.
I do not want to use bypass because I want to decrypt the communication to ChatGPT for information leakage prevention monitoring.
We are looking for a way to tune it so that it can be done without bypassing.
Questionably, it failed in Microsoft Edge, Google Chrome, and was usable in Firefox.
We are currently building a verification environment and will investigate.
I got documents about that
chatgpt using http2.0
so we need enable http2.0
please check below url
unfortunately I have another problem.. template Lx package does not work after 16.1.0 .. this configuration need over the 16.1.0 os version
Hi @neeeewbi and @LiefZimmerman
Sorry for the delayed response. I have checked to ensure that there are no issues with the actual modifications made.
I created a verification environment that closely resembles the actual service provision,
and after applying the settings,
I was able to confirm that it worked as expected, and ChatGPT was available for use.
made the following changes to the 'Client Profile' used in the 'SSL Configuration'.
Bigip Ver 16.1 (SSLo Ver 9.3)
SSL Forward Proxy > Hello Extensions
Application-Layer Protocol Negotiation Enable
The configuration I'm using in my SSLo involves decrypting HTTPS traffic, forwarding it to an explicit proxy (McAfee Web Gateway) for security inspection, and then re-encrypting it.
Enabling the ProxyALPN option allowed me to use the desired ChatGPT. However, all the traffic using HTTP/2 to communicate ceased flowing to the explicit proxy on the SSLo service chain side.
Is there a way to resolve this issue and restore the flow of traffic using HTTP/2 to the explicit proxy within the SSLo service chain?