We have been using the same API Calls for 7 years without issue. Over this past week, we started to get 406 errors. See below. Please let me know if you have any suggestions:
* About to connect() to secure.authorize.net port 443 (#0)
* Trying 198.241.207.102...
* Connected to secure.authorize.net (198.241.207.102) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate:
* subject: CN=*.authorize.net,O=Authorize.Net,L=Foster City,ST=California,C=US
* start date: Jan 24 23:02:59 2023 GMT
* expire date: Feb 24 23:02:58 2024 GMT
* common name: *.authorize.net
* issuer: CN=Entrust Certification Authority - L1K,OU="(c) 2012 Entrust, Inc. - for authorized use only",OU=See www.entrust.net/legal-terms,O="Entrust, Inc.",C=US
> post /gateway/transact.dll HTTP/1.1
> User-Agent: curl/7.29.0
> Host: secure.authorize.net
> Accept: */*
> Content-Length: 360
> Content-Type: application/x-www-form-urlencoded
>
* upload completely sent off: 360 out of 360 bytes
* HTTP 1.0, assume close after body
< HTTP/1.0 406 Not Acceptable
< Content-Type: text/html; charset=UTF-8
< Cache-Control: no-cache
< Pragma: no-cache
< Expires: 0
< Connection: close
<
* Closing connection 0
If you keep seeing this page, please contact support. Please provide your company name and other contact information
The 406 Not Acceptable error suggests an issue with the request content. Ensure the data format and content comply with the API's requirements. Check if the API endpoint expects specific headers or parameters. Additionally, confirm SSL certificates are valid. If issues persist, review the API documentation or contact the provider for further guidance.
01-29-2024 03:59 AM