FileStreamResult 无法识别 Asp.Net Core 2.2 中的多个 http 范围
FileStreamResult doesn't recognize multiple http ranges in Asp.Net Core 2.2
我有这么简单的端点:
[HttpGet]
public IActionResult GetFileDirect()
{
var path = ...; // path to the file
return File(System.IO.File.OpenRead(path), "text/plain", true);
}
当前文件内容:
abcdefghijklmnopqrstuvwxyz
正如您在 return 语句中看到的,我将 true
传递给 enableRangeProcessing
。在单一范围请求的情况下,它按预期工作:
curl -H Range:bytes=0-8 http://localhost:65318/api/File -i
这是回复:
HTTP/1.1 206 Partial Content
Content-Length: 9
Content-Type: text/plain
Content-Range: bytes 0-8/26
Accept-Ranges: bytes
Server: Kestrel
X-SourceFiles: =?UTF-8?B?QzpcVXNlcnNcY2ViaXlcRGVza3RvcFxSYW5nZVdlYlxSYW5nZVdlYlxhcGlcRmlsZQ==?=
X-Powered-By: ASP.NET
Date: Sat, 02 Nov 2019 17:46:49 GMT
abcdefghi
但是,在多范围请求的情况下,它不会考虑任何范围,并且会 return Ok
响应文件的完整内容:
curl -H Range:bytes=0-8,12-15 http://localhost:65318/api/File -i
这是回复:
HTTP/1.1 200 OK
Content-Length: 26
Content-Type: text/plain
Accept-Ranges: bytes
Server: Kestrel
X-SourceFiles: =?UTF-8?B?QzpcVXNlcnNcY2ViaXlcRGVza3RvcFxSYW5nZVdlYlxSYW5nZVdlYlxhcGlcRmlsZQ==?=
X-Powered-By: ASP.NET
Date: Sat, 02 Nov 2019 17:49:37 GMT
abcdefghijklmnopqrstuvwxyz
我比@Nkosi 更深入地研究了源代码以找到解析范围的位置,请查看AspNetCore - RangeHelper.cs
if (rawRangeHeader.Count > 1 || rawRangeHeader[0].IndexOf(',') >= 0)
{
logger.LogDebug("Multiple ranges are not supported.");
// The spec allows for multiple ranges but we choose not to support them because the client may request
// very strange ranges (e.g. each byte separately, overlapping ranges, etc.) that could negatively
// impact the server. Ignore the header and serve the response normally.
return (false, null);
}
我有这么简单的端点:
[HttpGet]
public IActionResult GetFileDirect()
{
var path = ...; // path to the file
return File(System.IO.File.OpenRead(path), "text/plain", true);
}
当前文件内容:
abcdefghijklmnopqrstuvwxyz
正如您在 return 语句中看到的,我将 true
传递给 enableRangeProcessing
。在单一范围请求的情况下,它按预期工作:
curl -H Range:bytes=0-8 http://localhost:65318/api/File -i
这是回复:
HTTP/1.1 206 Partial Content
Content-Length: 9
Content-Type: text/plain
Content-Range: bytes 0-8/26
Accept-Ranges: bytes
Server: Kestrel
X-SourceFiles: =?UTF-8?B?QzpcVXNlcnNcY2ViaXlcRGVza3RvcFxSYW5nZVdlYlxSYW5nZVdlYlxhcGlcRmlsZQ==?=
X-Powered-By: ASP.NET
Date: Sat, 02 Nov 2019 17:46:49 GMT
abcdefghi
但是,在多范围请求的情况下,它不会考虑任何范围,并且会 return Ok
响应文件的完整内容:
curl -H Range:bytes=0-8,12-15 http://localhost:65318/api/File -i
这是回复:
HTTP/1.1 200 OK
Content-Length: 26
Content-Type: text/plain
Accept-Ranges: bytes
Server: Kestrel
X-SourceFiles: =?UTF-8?B?QzpcVXNlcnNcY2ViaXlcRGVza3RvcFxSYW5nZVdlYlxSYW5nZVdlYlxhcGlcRmlsZQ==?=
X-Powered-By: ASP.NET
Date: Sat, 02 Nov 2019 17:49:37 GMT
abcdefghijklmnopqrstuvwxyz
我比@Nkosi 更深入地研究了源代码以找到解析范围的位置,请查看AspNetCore - RangeHelper.cs
if (rawRangeHeader.Count > 1 || rawRangeHeader[0].IndexOf(',') >= 0)
{
logger.LogDebug("Multiple ranges are not supported.");
// The spec allows for multiple ranges but we choose not to support them because the client may request
// very strange ranges (e.g. each byte separately, overlapping ranges, etc.) that could negatively
// impact the server. Ignore the header and serve the response normally.
return (false, null);
}