Getting 404 Error from cloudfront on correct API request

API Spot/Margin API
, , ,
1

I send GET https://api.binance.com/api/v3/ticker/24hr?symbol=AVAUSDT request using my application and receive null value with the following error HTTP/2 404 Error from cloudfront

‘url’ => ‘/v3/ticker/24hr’,
‘method’ => ‘GET’,
‘params’ => [
‘symbol’ => ‘DOTUSDT’,
],
‘header’ => 'HTTP/2 404
content-length: 48
date: Tue, 30 May 2023 00:56:45 GMT
server: nginx
strict-transport-security: max-age=31536000; includeSubdomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
172.27.0.49 - 30/May/2023:00:56:45 +0000 “POST /index.php” 400
x-content-type-options: nosniff
content-security-policy: default-src ‘self’
x-content-security-policy: default-src ‘self’
x-webkit-csp: default-src ‘self’
cache-control: no-cache, no-store, must-revalidate
pragma: no-cache
expires: 0
x-cache: Error from cloudfront
via: 1.1 1be5216f770ec05deb91e9e25b61b898.cloudfront.net (CloudFront)
x-amz-cf-pop: HEL51-P1
x-amz-cf-id: GtJPyyl7AdOf5NuwcfJkk8siILTbX1-87mhW05Hb3ODPjr4nRUGjjA==

',

Binance API works properly as using curl request or postman GET request I receive correct data no errors. My application sends exactly the same request and params as postman or curl but some strange error from cloudfront appears

My application is not using cloudfront, VPS provider neither so it seems my request goes to Binance cloud front then to Binance and then Binance responds to cloudfront and then cloudfront returns my application corrupted data

Can anyone suggest me what should I do to solve the issue?

2

It’s difficult to help without knowing how is your application sending the request. Please try to have a minimum script that just do the http request, it should be helpful to debug.

if you sending a GET, try to append parameters in url.