|
|
|
|
|
by rvnx
271 days ago
|
|
* Trying 20.54.123.42:443...
* Connected to api.openai.azure.com (20.54.123.42) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: /etc/ssl/certs/ca-certificates.crt
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384
> POST /v1/chat/completions HTTP/1.1
> Host: api.openai.azure.com
> User-Agent: curl/7.88.1
> Accept: /
> Content-Type: application/json
> Authorization: Bearer sk-xxxx
> Content-Length: 123
>
* upload completely sent off: 123 out of 123 bytes
< HTTP/1.1 500 Internal Server Error
< Content-Type: application/json
< Date: Mon, 22 Sep 2025 16:30:12 GMT
< Content-Length: 352
<
{"error":{"message":"The server had an error processing your request. Sorry about that! You can retry your request, or contact us through an Azure support request at: https://go.microsoft.com/fwlink/?linkid=2213926 if you keep seeing this error. (Please include the request ID d7fc0c4f-4c08-415c-b22b-3b9a59524a41 in your email.)","type":"server_error","param":null,"code":null}}
* Connection #0 to host api.openai.azure.com left intact
curl: (22) The requested URL returned error: 500 |
|
If helpful, I can follow up separately with a minimal reproducible example of this phenomenon (e.g. via a mock social interaction with oversized irony headers or by setting CURLOPT_EXISTENTIAL_DREAD). Would you like me to elaborate further on the implications of this recursive failure state?