Content negotiation and the Accept header.
内容协商与Accept报头。
HTTP content negotiation for different data formats.
HTTP内容作为不同数据格式的中介。
Content negotiation using resource handlers and scripting.
使用资源处理程序和脚本的内容协商。
The point, of course, is to demonstrate content negotiation.
当然，其重点是演示内容协商。
In addition, media type is just one content negotiation type.
此外，媒体类型只是一种内容协商类型。
The User-Agent header can also be used for content negotiation.
User - Agent标头也可用于内容协商。
Content negotiation is an important part of RESTful architecture.
内容协商是基于REST的体系结构中的一个重要部分。
These other headers are often used to enhance content negotiation.
另外，下列标头通常用来增强内容协商。
Content negotiation using custom handlers and regular expressions.
使用自定义处理程序和正则表达式的内容协商。
Using headers for content negotiation separates IT concerns from business ones.
将标头用于内容协商可将IT问题与业务问题分开。
Content negotiation is the idea that a single resource can have multiple data representations.
内容协商的理念是单个资源可具有多个数据表示形式。
It is worth mentioning that content negotiation is sometimes non-normatively done using the URI.
值得一提的是，有时使用URI 对内容协商执行非规范处理。
Technologies to enable the parallel Web include the HTML link element and HTTP content negotiation.
支持并行web的技术包括HTMLlink元素以及HTTP内容协商。
Content negotiation itself requires the maintenance of moderately complex server-side configurations.
内容协商本身要求维护中等复杂的服务器端配置。
A more semantically elegant method is to take advantage of the HTTP headers to do content negotiation.
更好的语义方法是利用HTTP报头进行内容协商。
The Resources in this article contain links to more detail on behind-the-scenes HTTP content negotiation.
本文的参考资料包含指向有关幕后HTTP 内容协商的更多细节的链接。
But few sites actually include content negotiation configurations and alternate representations of resources.
但是，很少有站点真正包括内容协商配置和交替资源表示。
For illustrative purposes, let's also imagine that Citibank used content negotiation on the user's account URL.
为了更好地说明，再想象一下，假设Citibank在用户的帐户URL上使用内容协商。
Server-driven negotiation is very similar to the original content negotiation specification, with some improvements.
服务器驱动的协商非常类似于最初的内容协商规范，但是有一些改进。
You will see how to use content negotiation to further a meaningful Web for humans and machines later in this article.
在本文后面的内容中，您将看到如何使用内容协商使对人和机器都有意义的Web走得更远。
Declarative support for content negotiation works well and the default resource life-cycle encourages a stateless approach.
对内容协商的声明式支持也工作得很好，默认的资源生命周期鼓励无状态的方式。
In this discussion, we will focus on how content negotiation is configured using the popular Apache HTTP Web server software.
在本文的讨论中，我们将关注如何使用流行的ApacheHTTPWeb服务器软件配置内容协商。
The MIME-type information is used by the service provider (content negotiation) to understand what sort of information it has received.
服务供应商会使用(内容协商)MIME类型信息来了解它所接受到信息的种类。
HTTP content negotiation uses short floating point numbers to indicate the relative importance, or weight, of various negotiable parameters.
HTTP内容协商使用短浮点数来表示各种可协商参数的相对重要性（或权重）。
As with content negotiation, the link element has gone through some evolutionary stages in order to meet the requirements for a parallel Web.
和内容协商类似，为了满足并行web的需求，link元素也经历了一些演变阶段。
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.
这种问题已经超出了协议无关的URI语法的范围，这得由HTTP协议提供内容协商作为解决方案。
Apache provides a content negotiation module that has two methods to select resource variants depending on the HTTP request: type maps and MultiViews.
Apache提供了一个内容协商模块，其中有两个方法可用于根据以下HTTP请求选择资源的变种：类型映射(type map)和MultiViews。
Content negotiation: Explore how HTTP 1.1 specifies to select the best representation for a given response when multiple representations are available.
内容协商：探索当存在多种可用表示时，HTTP 1.1如何规定为给定响应选择最佳表示。
In the first article we learned about how REST's URL naming schemes and content negotiation allow us to unify access to our documents, data and services.
在第一篇文章中，我们了解到REST的URL命名规范和内容协商如何让我们以统一的方式来访问文档、数据和服务。
This article addresses what is referred to as server-driven content negotiation. The specification also discusses two other types of content negotiation.
本文将重点讲述什么是服务器驱动的内容协商。
应用推荐