当然，其重点是演示内容协商。
The point, of course, is to demonstrate content negotiation.
内容协商与Accept报头。
查询参数常常用于内容协商。
使用资源处理程序和脚本的内容协商。
此外，媒体类型只是一种内容协商类型。
In addition, media type is just one content negotiation type.
另外，下列标头通常用来增强内容协商。
These other headers are often used to enhance content negotiation.
使用自定义处理程序和正则表达式的内容协商。
Content negotiation using custom handlers and regular expressions.
内容协商本身要求维护中等复杂的服务器端配置。
Content negotiation itself requires the maintenance of moderately complex server-side configurations.
将标头用于内容协商可将IT问题与业务问题分开。
Using headers for content negotiation separates IT concerns from business ones.
更好的语义方法是利用HTTP报头进行内容协商。
A more semantically elegant method is to take advantage of the HTTP headers to do content negotiation.
User - Agent标头也可用于内容协商。
The User-Agent header can also be used for content negotiation.
内容协商的理念是单个资源可具有多个数据表示形式。
Content negotiation is the idea that a single resource can have multiple data representations.
内容协商是基于REST的体系结构中的一个重要部分。
Content negotiation is an important part of RESTful architecture.
但是，很少有站点真正包括内容协商配置和交替资源表示。
But few sites actually include content negotiation configurations and alternate representations of resources.
本文将重点讲述什么是服务器驱动的内容协商。
This article addresses what is referred to as server-driven content negotiation. The specification also discusses two other types of content negotiation.
值得一提的是，有时使用URI 对内容协商执行非规范处理。
It is worth mentioning that content negotiation is sometimes non-normatively done using the URI.
服务器驱动的协商非常类似于最初的内容协商规范，但是有一些改进。
Server-driven negotiation is very similar to the original content negotiation specification, with some improvements.
支持并行web的技术包括HTMLlink元素以及HTTP内容协商。
Technologies to enable the parallel Web include the HTML link element and HTTP content negotiation.
本文的参考资料包含指向有关幕后HTTP内容协商的更多细节的链接。
The Resources in this article contain links to more detail on behind-the-scenes HTTP content negotiation.
服务供应商会使用(内容协商)MIME类型信息来了解它所接受到信息的种类。
The MIME-type information is used by the service provider (content negotiation) to understand what sort of information it has received.
对内容协商的声明式支持也工作得很好，默认的资源生命周期鼓励无状态的方式。
Declarative support for content negotiation works well and the default resource life-cycle encourages a stateless approach.
HTTP内容协商使用短浮点数来表示各种可协商参数的相对重要性（或权重）。
HTTP content negotiation uses short floating point numbers to indicate the relative importance, or weight, of various negotiable parameters.
例如，如果请求含有JSON数据，内容协商器会找到JSON格式化器。
For example, if the request contains JSON data, the content negotiator looks for a JSON formatter.
如果未找到匹配，内容协商器会尝试匹配请求体的媒体类型(有请求体时)。
If no matches are found, the content negotiator tries to match on the media type of the request body, if any.
为了更好地说明，再想象一下，假设Citibank在用户的帐户URL上使用内容协商。
For illustrative purposes, let's also imagine that Citibank used content negotiation on the user's account URL.
内容协商：探索当存在多种可用表示时，HTTP 1.1如何规定为给定响应选择最佳表示。
Content negotiation: Explore how HTTP 1.1 specifies to select the best representation for a given response when multiple representations are available.
如果仍无匹配，内容协商器便简单地捡取能够对类型进行序列化的第一个格式化器。
If there are still no matches, the content negotiator simply picks the first formatter that can serialize the type.
和内容协商类似，为了满足并行web的需求，link元素也经历了一些演变阶段。
As with content negotiation, the link element has gone through some evolutionary stages in order to meet the requirements for a parallel Web.
其次，内容协商器要考查每个格式化器，并评估此格式化器与HTTP请求的匹配好坏。
Next, the content negotiator looks at each formatter and evaluates how well it matches the HTTP request.
这种问题已经超出了协议无关的URI语法的范围，这得由HTTP协议提供内容协商作为解决方案。
Such questions are out of scope of the protocol-independent URI syntax, it's up to the HTTP protocol to provide content negotiation as a solution.
应用推荐