使用带范围说明符的HTTP范围头，而不是字节?-UsingtheHTTPRangeHeaderwitharangespecifierotherthanbytes?

32  

Absolutely - you are free to specify any range units you like.

绝对-你可以自由指定任何你喜欢的范围单位。

From RFC 2616:

RFC 2616:

3.12 Range Units

3.12单位范围

HTTP/1.1 allows a client to request that only part (a range of) the
response entity be included within the response. HTTP/1.1 uses range units in the Range (section 14.35) and Content-Range (section 14.16)
header fields. An entity can be broken down into subranges according to various structural units.

HTTP/1.1允许客户端请求响应中只包含响应实体的一部分(范围)。HTTP/1.1使用范围单元(第14.35节)和内容范围(第14.16节)头字段。一个实体可以根据不同的结构单元分解成子程序。

  range-unit       = bytes-unit | other-range-unit
  bytes-unit       = "bytes"
  other-range-unit = token

The only range unit defined by HTTP/1.1 is "bytes". HTTP/1.1
implementations MAY ignore ranges specified using other units.

HTTP/1.1定义的唯一范围单元是“字节”。HTTP/1.1实现可以忽略使用其他单元指定的范围。

The key piece is the last paragraph. Really what it's saying is that when they wrote the spec for HTTP/1.1, they only outlined the "bytes" token. But, as you can see from the 'other-range-unit' bit, you are free to come up with your own token specifiers.

关键是最后一段。它真正的意思是，当他们为HTTP/1.1编写规范时，他们只列出了“字节”标记。但是，正如您从“其他范围单元”位中看到的，您可以自由地提出自己的令牌说明符。

Coming up with your own Range specifiers does mean that you have to have control over the client and server code that uses that specifier. So, if you own the backend piece that exposes the "/document/content/http-range-question" URI, you are good to go; presumably you're using a modern web framework that lets you inspect the request headers coming in. You could then look at the Range values to perform the backing query correctly.

提供您自己的范围说明符意味着您必须控制使用该说明符的客户端和服务器代码。因此，如果您拥有公开“/document/content/http-range-question”URI的后端部分，那么您可以使用;假设您正在使用一个现代的web框架，它允许您检查传入的请求头。然后，您可以查看范围值，以正确执行支持查询。

Furthermore, if you control the AJAX code that makes requests to the backend, you should be able to set the Range header yourself.

此外，如果您控制了向后端发出请求的AJAX代码，您应该能够自己设置范围标题。

However, there is a potential downside which you anticipate in your question: the potential to break caching. If you are using a custom Range unit, any caches between your client and the origin servers "MAY ignore ranges specified using [units other than 'bytes']". So for example, if you had a Squid/Varnish cache between the front and backend, there's no guarantee that the results you're hoping for will be served from the cache!

但是，在您的问题中有一个潜在的缺点:可能破坏缓存。如果您正在使用自定义范围单元，那么您的客户端和源服务器之间的任何缓存“可能会忽略使用[除'bytes'之外的单元]指定的范围”。例如，如果你有一个鱿鱼/清漆缓存之间的前端和后端，没有保证你希望的结果将服务于缓存!

You might also consider an alternative implementation where, rather than using a query string, you make the page a "parameter" of the URI; e.g.: /document/content/http-range-question/page/1. This would likely be a little more work for you server-side, but it's HTTP/1.1 compliant and caches should treat it properly.

您还可以考虑另一种实现，即不使用查询字符串，而是将页面设置为URI的“参数”;例如:/文档/内容/ http-range-question / / 1页。对于服务器端来说，这可能需要做更多的工作，但是它是兼容HTTP/1.1的，缓存应该正确地对待它。

Hope this helps.

希望这个有帮助。

0  

HTTP Range is typically used for recovering interrupted downloads without starting from the beginning.

HTTP Range通常用于从一开始就恢复被中断的下载。

What you're trying to do would be better handled by OAI-ORE, which allows you to define relationships between multiple documents. (alternative formats, components of the whole, etc)

您正在尝试做的事情最好由OAI-ORE来处理，它允许您定义多个文档之间的关系。(可选格式、整体组件等)

Unfortunately, it's a relatively new metadata format, and I don't know of any web browsers that ship with native support.

不幸的是，它是一种相对较新的元数据格式，我不知道有任何web浏览器附带本机支持。

0  

bytes is the only unit supported by HTTP 1.1 Specification.

字节是HTTP 1.1规范支持的惟一单元。

-2  

It sounds like you want to change the HTTP spec just to remove a querystring parameter. In order to do this you'd have to modify code on both the client to send the modified header and the server to read from the "Range" header instead of the querystring.

听起来您想要更改HTTP规范，只是为了删除一个querystring参数。为了做到这一点，您必须修改客户机上的代码，以便将修改后的头和服务器从“范围”头(而不是querystring)中读取。

The end result is that this will probably work, but you're breaking all of the standards and existing tools to do so.

最终的结果是，这可能会起作用，但是您违反了所有的标准和现有的工具。