Laravel使用Guzzle携带Access Token调用API返回空页问题排查
问题场景
- 在Laravel项目中使用Guzzle调用自有API,使用Postman直接调用该API接口时全流程正常,但从Laravel发起请求后经过长时间等待,最终仅返回空白页面
- 对照测试Guzzle调用其他公开API(如httpbin测试接口)时,功能完全正常,可正常获取响应内容
- 额外调试现象:使用Postman访问该自有服务的非API页面时,直接报错
Could not get response Parse Error: Invalid character in chunk size - 核心疑问:是否遗漏了相关配置或存在操作失误?
相关测试代码
自有API调用代码(异常场景)
$url = 'http://myapi.me/api/get?param=123'; $client = new Client(); $res = $client->request('GET', $url, [ 'headers' => [ 'Authorization' => 'Bearer xxxxxxxx', ] ]);
公开API调用代码(正常场景)
$url = 'http://httpbin.org/get'; $client = new Client(); $res = $client->request('GET', $url);
调试输出
在Laravel中通过dd()打印Guzzle返回的响应对象,输出结构如下:
GuzzleHttp\Psr7\Response {#298 ▼ -reasonPhrase: "OK" -statusCode: 200 -headers: array:15 [▼ "Date" => array:1 [▶] "Content-Type" => array:1 [▶] "Transfer-Encoding" => array:1 [▶] "Connection" => array:1 [▶] "Set-Cookie" => array:1 [▶] "Cache-Control" => array:1 [▶] "X-RateLimit-Limit" => array:1 [▶] "X-RateLimit-Remaining" => array:1 [▶] "Access-Control-Allow-Origin" => array:1 [▶] "CF-Cache-Status" => array:1 [▶] "cf-request-id" => array:1 [▶] "Report-To" => array:1 [▶] "NEL" => array:1 [▶] "Server" => array:1 [▶] "CF-RAY" => array:1 [▶] ] -headerNames: array:15 [▼ "date" => "Date" "content-type" => "Content-Type" "transfer-encoding" => "Transfer-Encoding" "connection" => "Connection" "set-cookie" => "Set-Cookie" "cache-control" => "Cache-Control" "x-ratelimit-limit" => "X-RateLimit-Limit" "x-ratelimit-remaining" => "X-RateLimit-Remaining" "access-control-allow-origin" => "Access-Control-Allow-Origin" "cf-cache-status" => "CF-Cache-Status" "cf-request-id" => "cf-request-id" "report-to" => "Report-To" "nel" => "NEL" "server" => "Server" "cf-ray" => "CF-RAY" ] -protocol: "1.1" -stream: GuzzleHttp\Psr7\Stream {#296 ▼ -stream: stream resource @9 ▶} -size: null -seekable: true -readable: true -writable: true -uri: "php://temp" -customMetadata: [] } }
问题排查与解决方案
- 核心异常根源:从响应头的CF-*字段可判断,该自有API通过Cloudflare代理接入。当前拿到的200状态码为代理层返回的通用响应,实际源站服务输出的chunked分块格式不符合HTTP 1.1规范,导致响应体解析失败
- 现象对应逻辑:
- Postman的chunked解析容错率高于Guzzle,因此调用API接口时可以正常拿到内容,但访问非API页面时分块错误更明显,就会直接抛出
Invalid character in chunk size报错,说明源站输出的分块大小标识中混有非法字符(如前置空白、BOM头、无关输出) - Guzzle默认开启chunked自动解码,遇到格式错误时不会抛出致命异常,只会正常解析状态码和响应头,实际响应体的流因校验失败被置空,最终表现为页面空白
- 调用
$res->getBody()->getContents()可验证这一点,返回值通常为空字符串
- Postman的chunked解析容错率高于Guzzle,因此调用API接口时可以正常拿到内容,但访问非API页面时分块错误更明显,就会直接抛出
- 可落地的修复步骤:
- 跳过Cloudflare代理,直接通过源站IP发起Guzzle请求验证,确认是否为代理层的格式篡改问题
- 检查自有API源站的输出逻辑:关闭所有框架层的无关调试输出、空白换行、BOM头,确保分块传输的格式严格符合规范
- Guzzle端做临时兼容处理:在请求配置中关闭自动内容解码,手动读取原始响应流,示例代码:
$res = $client->request('GET', $url, [ 'headers' => [ 'Authorization' => 'Bearer xxxxxxxx', ], 'decode_content' => false, ]); $rawContent = (string) $res->getBody();- 调整Cloudflare代理配置:关闭不必要的内容压缩、自动格式转换功能,避免代理层篡改响应的分块结构
内容的提问来源于stack exchange,提问作者luca ditrimma
相关产品推荐
相关产品推荐

