切换到HTTPS后Express res.write()流式响应失效问题

核心原因 #

Nginx在SSL模式下默认开启响应缓冲，会将所有分块响应缓存至请求处理完成后一次性发送，破坏了流式输出的实时性逻辑。

解决方案 #

1. 完善Nginx HTTPS配置并关闭缓冲 #

现有配置仅包含HTTP转HTTPS规则，需补充完整的HTTPS服务配置，强制关闭代理缓冲以确保分块响应实时推送：

server {
    listen 443 ssl;
    server_name api.domain.com;

    # 替换为Certbot生成的实际证书路径
    ssl_certificate /etc/letsencrypt/live/api.domain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/api.domain.com/privkey.pem;

    # 关闭代理缓冲，禁用响应缓存
    proxy_buffering off;
    # 强制启用分块传输编码
    chunked_transfer_encoding on;

    location / {
        proxy_pass http://localhost:8000; # 指向你的Express服务地址
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }
}

# 保留HTTP转HTTPS规则
server {
    if ($host = api.domain.com) {
        return 301 https://$host$request_uri;
    }
    listen 80;
    server_name api.domain.com;
    return 404;
}

2. 调整Express响应配置 #

• 移除无效的response.flush = () => {}，Express中无需手动定义空flush方法；
• 统一响应内容类型与客户端请求头，优化状态码及缓存控制：

response.writeHead(200, {
    "Content-Type": "text/event-stream; charset=utf-8",
    "Transfer-Encoding": "chunked",
    "X-Content-Type-Options": "nosniff",
    "Cache-Control": "no-cache",
    "Connection": "keep-alive"
});

3. 优化流式写入逻辑 #

response.write()为同步操作，无需添加await，同时添加换行符方便客户端分割响应块：

if (urlsBatch.length === 5) {
    response.write(JSON.stringify(urlsBatch) + '\n');
    console.log(urlsBatch);
    urlsBatch = [];
}

4. 客户端响应处理微调 #

按行分割响应块，避免多chunk拼接导致JSON解析失败：

const chunk = new TextDecoder().decode(value);
const lines = chunk.split('\n').filter(line => line.trim());
lines.forEach(line => {
    try {
        const links = JSON.parse(line);
        console.log(links);
        // setLinks((curr) => [...curr, ...links]);
    } catch (e) {
        console.error('Chunk解析失败:', e);
    }
});

内容的提问来源于stack exchange，提问作者mursal rabb