Forum Discussion
neeeewbie
MVP
MVPchatgpt sent 403 forbidden response code when client access via sslo
Hi guys
I need your help !
chatgpt sent 403 forbidden response code when client access via sslo
I guess chatgpt API connection can't established becuase of proxy setting
please let me know the reason
thank you
- LiefZimmerman
Admin
neeeewbie and/or sugiyama_san - is there one or more replies that you may Accept As Solution? Seems like the thread may not be done but...even a partial solution (or further update?) could help future users trying to leverage ChatGPT.
Thanks, Lief
neeeewbiefirefox browser user can access the chatGPT without http2 profile
other browser need http2 profile
sugiyama_sanAltocumulus
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
Extentions List...
Application-Layer Protocol Negotiation EnableThanks!!
- Kevin_Stewart
Employee
Late to the scene...
Officially, ChatGPT through SSLO requires HTTP/2. The Proxy ALPN option was added in SSLO 9.0: https://clouddocs.f5.com/sslo-deployment-guide/sslo-09/chapter1/page1.02.html
- sugiyama_san
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?
- Kevin_Stewart
HTTP/2 to an inline HTTP inspection device is not supported.
- LiefZimmerman
Thanks Kevin_Stewart - your expertise is always appreciated.
neeeewbie - can you mark one or more of these as Solutions?
