Why my fetch request always get empty response.

[adoin]

Here is my nginx config for test

pid D:/workspace/anubis-defend-demo/logs/nginx.pid;

events {
    worker_connections  1024;
}

http {
    include       D:/nginx-1.28.0/conf/mime.types;
    default_type  application/octet-stream;
    sendfile        on;
    keepalive_timeout  65;

    # 临时目录配置
    client_body_temp_path D:/workspace/anubis-defend-demo/temp/client_body_temp;
    proxy_temp_path D:/workspace/anubis-defend-demo/temp/proxy_temp;
    fastcgi_temp_path D:/workspace/anubis-defend-demo/temp/fastcgi_temp;
    uwsgi_temp_path D:/workspace/anubis-defend-demo/temp/uwsgi_temp;
    scgi_temp_path D:/workspace/anubis-defend-demo/temp/scgi_temp;

    # 错误日志配置
    error_log D:/workspace/anubis-defend-demo/logs/error.log;
    access_log D:/workspace/anubis-defend-demo/logs/access.log;

    server {
        listen 4545;
        server_name localhost;

        root D:/workspace/anubis-defend-demo/dist;
        index index.html;

        # 静态资源缓存
        location /assets {
            expires 1y;
            add_header Cache-Control "public";
        }

        # 前端主路由，保留缓存头，移除多余CORS和OPTIONS
        location / {
            try_files $uri $uri/ /index.html;
            add_header Cache-Control "no-cache, must-revalidate";
        }

        error_page 500 502 503 504 /50x.html;
        location = /50x.html {
            root D:/workspace/anubis-defend-demo/dist;
        }
    }

    server {
        listen 9090;
        server_name localhost;

        # 保留自定义API测试路由（如需调试CORS可单独保留）
        location /api/test {
            add_header 'Access-Control-Allow-Origin' 'http://localhost:4545' always;
            add_header 'Access-Control-Allow-Credentials' 'true' always;
            add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS, PUT, DELETE' always;
            add_header 'Access-Control-Allow-Headers' 'DNT,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type,Range,Authorization' always;
            add_header 'Access-Control-Expose-Headers' 'Content-Length,Content-Range' always;
            add_header 'Access-Control-Max-Age' 1728000 always;

            if ($request_method = 'OPTIONS') {
                return 204;
            }

            default_type application/json;
            return 200 '{"message": "Hello from nginx fake API"}';
        }
    }
} 

And I deploy two anubis on both web and api through docker:

docker stop anubis-api
docker rm anubis-api
docker run -d --name anubis-api `
  -p 8080:80 `
  -e TARGET=http://host.docker.internal:9090 `
  -e BIND=0.0.0.0:80 `
  -e USE_REMOTE_ADDRESS=true `
  -e ED25519_PRIVATE_KEY_HEX=3cfee5543f145b0d9fd88eb833860c11c9c5158faf0dded9548bf097f1bf3f8c `
  ghcr.io/techarohq/anubis:latest

docker stop anubis-web
docker rm anubis-web
docker run -d --name anubis-web `
  -p 80:80 `
  -e TARGET=http://host.docker.internal:4545 `
  -e BIND=0.0.0.0:80 `
  -e USE_REMOTE_ADDRESS=true `
  -e ED25519_PRIVATE_KEY_HEX=3cfee5543f145b0d9fd88eb833860c11c9c5158faf0dded9548bf097f1bf3f8c `
  ghcr.io/techarohq/anubis:latest

There is a button on web html that do this:

 const testApiCall = async () => {
  try {
    const response = await fetch('http://localhost:8080/api/test', {
      method: 'GET',
      credentials: 'include'
    });
    console.log('res',response)
    const data = await response.json();
    console.log('API响应:', data);
  } catch (error: any) {
    console.error('API调用失败:', error);
    alert('API调用失败: ' + error.message);
  }
}

But I always get empty response.
I can se the cookie is good

But response nothing, and show error "Failed to fetch"

[adoin]

What should I do, or am I doing the things as expected?

[prettysunflower]

We would need to test on our machine, but wouldn't the problem be related to CORS? You're setting a Access-Control-Allow-Origin to localhost:4545, while your screenshot indicates that your host is localhost:8080.
If the problem is related to Anubis, note that it would very probably throw a 502 Bad Gateway error on the request in the Network tab of your developer tools if it can't reach upstream (does your request response code appears on the network tab?)

[adoin]

We would need to test on our machine, but wouldn't the problem be related to CORS? You're setting a Access-Control-Allow-Origin to localhost:4545, while your screenshot indicates that your host is localhost:8080. If the problem is related to Anubis, note that it would very probably throw a 502 Bad Gateway error on the request in the Network tab of your developer tools if it can't reach upstream (does your request response code appears on the network tab?)

Thank you for reply, I finally found the fake api on 9090 is bad. So it's nothing todo with Anubis.
Not CORS issue for now.