Nginx反向代理对Flutter返回400错误，Postman请求正常

相关配置与代码 #

Nginx配置（nginx.conf）

worker_processes auto;
events {
    worker_connections 1024;
}

http {
    log_format custom '$remote_addr - $remote_user [$time_local] "$request" '
    '$status $body_bytes_sent "$http_referer" '
    '"$http_user_agent" "$http_x_forwarded_for" $request_time';

    proxy_cache_path /tmp/nginx levels=1:2 keys_zone=my_zone:10m inactive=60m;
    proxy_cache_key "$scheme$request_method$host$request_uri";

    default_type application/octet-stream;
    include /etc/nginx/mime.types;

    sendfile on;
    tcp_nopush on;
    tcp_nodelay on;
    keepalive_timeout 65;
    types_hash_max_size 4096;
    
    upstream my-django-rest-api {
        server 172.16.16.1:8080; # 内部Django API服务
    }

    server {
        listen 1652;
        access_log /var/log/nginx/access.log custom;
        error_log /var/log/nginx/error.log;

        location / {
            proxy_pass http://my-django-rest-api;
            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;
            
            proxy_cache my_zone;
            add_header X-Proxy-Cache $upstream_cache_status;
            proxy_buffering on;
            proxy_cache_valid 200 302 60m;
            proxy_cache_valid 404 1m;

            # WebSocket支持 (nginx 1.4)
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection "upgrade";
        }
    }
}

Postman GET请求头

Key                      Value
Host                     <calculated when request is sent>
User-Agent               PostmanRuntime/7.42
Accept                   */*
Accept Encoding          gzip,deflate,br
Connection               keep-alive
Authorization            Token f384996c63b4****************

Flutter请求核心代码

Future<HttpieResponse> get(url,
      {Map<String, String>? headers,
      Map<String, dynamic>? queryParameters,
      bool? appendLanguageHeader,
      bool? appendAuthorizationToken}) async {
    var finalHeaders = _getHeadersWithConfig(
        headers: headers,
        appendLanguageHeader: appendLanguageHeader,
        appendAuthorizationToken: appendAuthorizationToken);

    if (queryParameters != null && queryParameters.keys.isNotEmpty) {
      url = url + _makeQueryString(queryParameters);
    }

    Response? response;
    try {
      response = await client.get(Uri.parse(url), headers: finalHeaders);
    } catch (error) {
      _handleRequestError(error);
    }

    if (response != null) {
      return HttpieResponse(response);
    }
    throw ();
  }
      
  Map<String, String> _getHeadersWithConfig(
      {Map<String, String>? headers = const {},
      bool? appendLanguageHeader,
      bool? appendAuthorizationToken}) {
    headers = headers ?? {};
    Map<String, String> finalHeaders = Map.from(headers);

    appendLanguageHeader = appendLanguageHeader ?? true;
    appendAuthorizationToken = appendAuthorizationToken ?? false;

    if (appendLanguageHeader) finalHeaders['Accept-Language'] = _getLanguage();
    if (appendAuthorizationToken && authorizationToken != null) {
      finalHeaders['Authorization'] = 'Token $authorizationToken';
    }
    if (magicHeaderName != null && magicHeaderValue != null) {
      finalHeaders[magicHeaderName!] = magicHeaderValue!;
    }

    return finalHeaders;
  }

  String _getLanguage() {
    return _localizationService.getLocale().languageCode.toLowerCase();
  }

.env.json配置

{
  "API_URL": "http://24.XX.XX.XX:70/",
  "MAGIC_HEADER_NAME": "",
  "MAGIC_HEADER_VALUE": "",
}

问题解答 #

1. 排查前端之前，Nginx端需要做哪些排查操作？ #

• 提升日志级别捕获完整请求头：修改Nginx配置的error_log为error_log /var/log/nginx/error.log debug;，重启Nginx后重新触发Flutter请求，查看debug日志中的完整无效头内容，获取比\x3a...更详细的信息。
• 检查Nginx版本：HTTP/1.1规范对请求头格式要求严格，部分旧版本Nginx对异常头的处理更苛刻。执行nginx -v确认版本，必要时升级到最新稳定版。
• 临时开启无效头忽略测试：在http或server块添加ignore_invalid_headers on;，重启Nginx后测试Flutter请求是否正常。如果正常，说明确实是前端发送了不符合规范的头，再针对性排查。
• 抓包对比请求差异：用tcpdump或Wireshark分别捕获Postman和Flutter的请求数据包，对比两者的请求头结构。例如执行tcpdump -i any port 1652 -w flutter_req.pcap抓取Flutter请求，直接对比原始HTTP头格式。
• 临时关闭WebSocket配置：当前Nginx配置中强制设置了WebSocket相关头，但Flutter发送的是普通GET请求，可能导致头格式冲突。临时注释掉proxy_http_version 1.1;、proxy_set_header Upgrade $http_upgrade;、proxy_set_header Connection "upgrade";这三行，重启后测试请求是否正常。

2. 日志中标记为无效的"\x3a..."头行具体是什么？ #

• \x3a是ASCII编码的冒号（:），日志里的"\x3a..."表示请求头中出现了以冒号开头的无效行，完全不符合HTTP请求头Key: Value的规范格式。
• 结合代码与配置分析：.env.json中MAGIC_HEADER_NAME为空字符串，而Flutter代码中只要magicHeaderName和magicHeaderValue不为null（空字符串不是null），就会添加一个空键的请求头，最终发送的头格式为: （冒号加空格），正好对应日志里的\x3a...内容。
• 这是Flutter代码的逻辑bug：当MAGIC_HEADER_NAME为空时，应该跳过添加这个头，而非添加空键的无效头。

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