document.write('&&&&');
请输入你要查询的地址：
更新TKD缓存
三月平均：19,436&&ALEXA数据预估流量：IP& 40,200 PV& 205,020
PR &&&&&&百度权重 &&&&&&百度快照 &&&&&&首页位置 &&&&&&外链
百度索引量:&&预计来路：&IP&&&&&&出站链接：5个
首页内链：4个
本站反链：--条
该网站IP：-- 地址：-- 有约 -- 个站点运行在此服务器上
一般不超过80个字符
网站关键词
酒店管理系统,微信预订,微博预订,酒店直销运营,垂直行业,酒店运营平台
一般不超过100个字符
皮皮酒店，打造社交化多平台酒店直销运营平台。
一般不超过200个字符
关键词排名分析
数据载入中，请稍候。
数据载入中，请稍候。
最近查询：&&&&&&&&&&&&&&&&&&&&
其他功能：
& 爱站网 版权所有
About Aizhan寻找单词要**ll**两个 **pp**** **cc** **tt** **mm**请大家填往*填字母!_百度作业帮
寻找单词要**ll**两个 **pp**** **cc** **tt** **mm**请大家填往*填字母!
类似这种单词不少,我每样给你5个吧!**ll**:willow,pillow,killer,follow,seller **pp****:supplier,happiest,sapphire,sapphist,sapphism,supports **cc**:soccer,buccal,succor,succot,buccan **tt**:little,cutter,bitter,butter,letter **mm**:hummer,summer,common,hummel,summon
pulledfilledhappenedsoccerbutterbummer
pillow 枕头follow 跟随happened 发生succor 援助者，救助者button 纽扣,按钮 summer 夏天summit 顶点,政府首脑的
followcommoncottercopperah
miller seller teller supplier supposed dippiest reccur succor succom better bitter cutter simmer hummer matter
taller fellow/pillowhappenedsoccerbuttercommon
followsupposedsoccertattoohummer
mellow,别的想不出
您可能关注的推广回答者：OriginServer]
M-GET /a-resource HTTP/1.1
Host: www.w3.org
Man: "http://www.w3.org/-CCPPexchange" ; ns=99
99-Profile: "/hw","/sw","1-uKhJE/AEeeMzFSejsYshHg=="
99-Profile-Diff-1: &?xml version="1.0"?>
&RDF xmlns="http://www.w3.org/TR/1999/PR-rdf-syntax-#"
xmlns:PRF="http://www.w3.org/TR/WD-profile-vocabulary#">
&Description ID="SoftwarePlatform" PRF:Sound="On" />
[2. OriginServer --> UserAgent (case of failure)]
HTTP/1.1 510 Not Extended
[3. OriginServer --> CCPPrepositories]
GET /hw HTTP/1.1
GET /sw HTTP/1.1
[4. OriginServer --> UserAgent]
HTTP/1.1 200 OK
Cache-control: no-cache
Content-Type: text/html
Content-Length: 1200
NOTE: If the Profile-Diff header field is too long, the request(1.) might
not be successful because some implementations of origin server/gateway/proxy
restrict the length of headers. The alternative is to transmit runtime changes
in an entity body. This solution is beyond the scope of the CC/PP exchange
[0. UserAgent --> OriginServer]
M-POST /a-resource HTTP/1.1
Man: "http://www.w3.org/-CCPPexchange" ; ns=99
99-Profile: "/hw","/sw","uKhJE/AEeeMzFSejsYshHg=="
Host: www.w3.org
Content-Type: text/xml
Content-Length: 258
&?xml version="1.0"?>
&RDF xmlns="http://www.w3.org/TR/1999/PR-rdf-syntax-#"
xmlns:PRF="http://www.w3.org/TR/WD-profile-vocabulary#">
&Description ID="SoftwarePlatform" PRF:Sound="On" />
The scenario is listed below.
The user agent issues an optional extension request(GET) with the Profile
header and the Profile-Diff header.
The origin server examines the extension declaration header(Opt) and
determines if it is supported for this message. If not, the origin server
ignores the extension headers, and sends back the non-tailored content.
Otherwise, the origin server gets the list of the absoluteURIs in the Profile
header field. After that the origin server issues requests to the CC/PP
repositories to get the CC/PP descriptions using these absoluteURIs.
The origin server generates the tailored content according to the enumerated
CC/PP descriptions, and sends back the tailored content.
The requests and responses according to the scenario is described
[1. UserAgent --> OriginServer]
GET /a-resource HTTP/1.1
Host: www.w3.org
Opt: "http://www.w3.org/-CCPPexchange" ; ns=19
19-Profile: "/hw","/sw","1-uKhJE/AEeeMzFSejsYshHg=="
19-Profile-Diff-1: &?xml version="1.0"?>
&RDF xmlns="http://www.w3.org/TR/1999/PR-rdf-syntax-#"
xmlns:PRF="http://www.w3.org/TR/WD-profile-vocabulary#">
&Description ID="SoftwarePlatform" PRF:Sound="On" />
[2. OriginServer --> UserAgent (case of failure)]
HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 1200
&!-- non-tailored content -->
[3. OriginServer --> CCPPrepositories]
GET /hw HTTP/1.1
GET /sw HTTP/1.1
[4. OriginServer --> UserAgent]
HTTP/1.1 200 OK
Cache-control: no-cache
Content-Type: text/html
Content-Length: 1200
The scenario is listed below.
The user agent issues a mandatory extension request(M-GET) with the Profile
header and the Profile-Diff header. According to the HTTP extension framework
specification for the hop-by-hop extension, C-Man, C-Opt, and all header
fields with matching header-prefix values defined by C-Man and C-Opt MUST be
protected by a Connection header field. In this example, "C-Man", "64-Profile"
and "64-Profile-Diff-1" are protected by the Connect header field.
The first-hop proxy examines the extension declaration header(C-Man) and
determines if it is supported for this message. If not, it responds with a
510(Not Extended) status code.
Otherwise, the first-hop proxy issues requests to the CC/PP repositories to
get the CC/PP descriptions using the absoluteURIs.
The first-hop proxy generates the request with the Accept, Accept-Charset,
Accept-Encoding and Accept-Language, using the enumerated CC/PP descriptions,
and issues the request to the origin server.
The origin server responds to the first-hop proxy with the content.
The first-hop proxy transforms the content into the tailored content using the
enumerated CC/PP descriptions. After that the first-hop proxy sends back the
tailored content with the mandatory hop-by-hop extension response
header(C-Ext).
The requests and responses according to the scenario is described
[1. UserAgent --> Proxy]
M-GET /a-resource HTTP/1.1
Host: www.w3.org
C-Man: "http://www.w3.org/-CCPPexchange" ; ns=64
64-Profile: "/hw", "/sw", "1-uKhJE/AEeeMzFSejsYshHg=="
64-Profile-Diff-1: &?xml version="1.0"?>
&RDF xmlns="http://www.w3.org/TR/1999/PR-rdf-syntax-#"
xmlns:PRF="http://www.w3.org/TR/WD-profile-vocabulary#">
&Description ID="SoftwarePlatform" PRF:Sound="On" />
Connection: C-Man, 64-Profile, 64-Profile-Diff-1
[2. Proxy --> UserAgent (case of failure)]
HTTP/1.1 510 Not Extended
[3. Proxy --> CCPPrepositories]
GET /hw HTTP/1.1
GET /sw HTTP/1.1
[4. Proxy --> OriginServer]
GET /a-resource HTTP/1.1
Host: www.w3.org
Accept: text/xml, text/html, */*
Accept-Charset: UTF-16, iso-2022-JP
Accept-Encoding: compress, gzip
Accept-Language: ja, en
[5. OriginServer --> Proxy]
HTTP/1.1 200 OK
Cache-control: no-cache
Content-Type: text/ charset=UTF-16
Content-Encoding: compress
Content-Language: ja
Content-Length: 1200
[6. Proxy --> UserAgent]
HTTP/1.1 200 OK
Cache-control: no-cache
Content-Type: text/ charset=UTF-16
Content-Encoding: compress
Content-Language: ja
Content-Length: 900
The scenario is listed below.
The user agent issues an optional extension request(GET) with the Profile
header and the Profile-Diff header.
The first-hop proxy examines the extension declaration header(C-Opt) and
determines if it is supported for this message. If not, the first-hop proxy
foreward requests to the origin server after the first-hop proxy get rid of
the headers which are listed in the Connection header.
Otherwise, the first-hop proxy issues requests to the CC/PP repositories to
get the CC/PP descriptions using the absoluteURIs.
The first-hop proxy generates the request and issues the request to the origin
The origin server responds to the first-hop proxy with the content.
The first-hop proxy transforms the content into the tailored content using the
enumerated CC/PP descriptions. After that the first-hop proxy sends back the
tailored content to the user agent.
The requests and responses according to the scenario is described
[1. UserAgent --> Proxy]
GET /a-resource HTTP/1.1
Host: www.w3.org
C-Opt: "http://www.w3.org/-CCPPexchange" ; ns=80
80-Profile: "/hw", "/sw", "1-uKhJE/AEeeMzFSejsYshHg=="
80-Profile-Diff-1: &?xml version="1.0"?>
&RDF xmlns="http://www.w3.org/TR/1999/PR-rdf-syntax-#"
xmlns:PRF="http://www.w3.org/TR/WD-profile-vocabulary#">
&Description ID="SoftwarePlatform" PRF:Sound="On" />
Connection: C-Opt, 80-Profile, 80-Profile-Diff-1
[2. Proxy --> OriginServer (case of failure)]
GET /a-resource HTTP/1.1
Host: www.w3.org
[3. Proxy --> CCPPrepositories]
GET /hw HTTP/1.1
GET /sw HTTP/1.1
[4. Proxy --> OriginServer]
GET /a-resource HTTP/1.1
Host: www.w3.org
Accept: text/xml, text/html, */*
Accept-Charset: UTF-16, iso-2022-JP
Accept-Encoding: compress, gzip
Accept-Language: ja, en
[5. OriginServer --> Proxy]
HTTP/1.1 200 OK
Cache-control: no-cache
Content-Type: text/ charset=UTF-16
Content-Encoding: compress
Content-Language: ja
Content-Length: 1200
[6. Proxy --> UserAgent]
HTTP/1.1 200 OK
Cache-control: no-cache
Content-Type: text/ charset=UTF-16
Content-Encoding: compress
Content-Language: ja
Content-Length: 900
The scenario is listed below.
The user agent issues a request.
The origin server issues requests to the CC/PP repositories to get the CC/PP
descriptions.
The CC/PP description is obtained successfully(200 OK) from
"/hw", while the CC/PP description could not be obtained
(404 Not Found) from "/sw".
The origin server generates the tailored content using only the CC/PP
description from "/hw", and sends back the tailored content
with the Profile-Warning response header. (when the origin server did not
obtain the fully&enumerated CC/PP descriptions, it depends on the
implementation whether the origin server should respond to the request with a
tailored content, a non-tailored content or an error.)
The requests and responses according to the scenario is described
[1. UserAgent --> OriginServer]
M-GET /a-resource HTTP/1.1
Host: www.w3.org
Man: "http://www.w3.org/-CCPPexchange" ; ns=25
25-Profile: "/hw", "/sw"
[2. OriginServer --> CCPPrepositories]
GET /hw HTTP/1.1
GET /sw HTTP/1.1
[3. CCPPrepositories --> OriginServer]
HTTP/1.1 200 OK;
HTTP/1.1 404 Not F;
[4. OriginServer --> UserAgent]
HTTP/1.1 200 OK
25-Profile-warning: 102 /sw "Not used profile",
202 www.w3.org "Content generation applied"
Cache-control: no-cache
Content-Type: text/html
Content-Length: 1200
The scenario is listed below.
The user agent issues a request.
The origin server issues requests to the CC/PP repositories to get the CC/PP
descriptions.
The origin server generates and sends back the tailored content. In this
example, the origin server indicates no-cache="Ext" and max-age=1200
directives in the Cache-control header field, which means the origin server
intends to use the HTTP cache expiration model. The Vary header and the
Expires header are also included. Therefore the response which is cached along
the request/response chain might be used without revalidation with the origin
server. The Profile-Diff header field does not have to be included in the Vary
header field because the change of the Profile-Diff header is&represented
by profile-diff-name "1-uKhJE/AEeeMzFSejsYshHg==" in the Profile header field.
The requests and responses according to the scenario is described
[1. UserAgent --> OriginServer]
M-GET /a-resource HTTP/1.1
Host: www.w3.org
Man: "http://www.w3.org/-CCPPexchange" ; ns=70
70-Profile: "/hw", "/sw", "1-uKhJE/AEeeMzFSejsYshHg=="
70-Profile-Diff-1: &?xml version="1.0"?>
&RDF xmlns="http://www.w3.org/TR/1999/PR-rdf-syntax-#"
xmlns:PRF="http://www.w3.org/TR/WD-profile-vocabulary#">
&Description ID="SoftwarePlatform" PRF:Sound="On" />
[2. OriginServer --> CCPPRepositories]
GET /hw HTTP/1.1
GET /sw HTTP/1.1
[3. OriginServer --> UserAgent]
HTTP/1.1 200 OK
Cache-control: max-age=1200, no-cache="Ext"
Vary: Man, 70-Profile
Expires: Tue, 05 Mar :00 GMT
Content-Type: text/html
Content-Length: 1200
The scenario is listed below.
The user agent issues a request.
The first-hop proxy issues requests to the CC/PP repositories to get the CC/PP
descriptions.
The first-hop proxy generates and issues a request to the origin server.
The origin server responds to the first-hop proxy with the content.
The first-hop proxy transforms and sends back a tailored content with the
Cache-control header, the Vary header and the Expires header. Therefore the
response might be used by the user agent without revalidation.
The requests and responses according to the scenario is described
[1. UserAgent --> Proxy]
M-GET /a-resource HTTP/1.1
Host: www.w3.org
C-Man: "http://www.w3.org/-CCPPexchange" ; ns=67
67-Profile: "/hw", "/sw", "1-uKhJE/AEeeMzFSejsYshHg=="
67-Profile-Diff-1: &?xml version="1.0"?>
&RDF xmlns="http://www.w3.org/TR/1999/PR-rdf-syntax-#"
xmlns:PRF="http://www.w3.org/TR/WD-profile-vocabulary#">
&Description ID="SoftwarePlatform" PRF:Sound="On" />
Connection: C-Man, 67-Profile
[2. Proxy --> CCPPrepositories]
GET /hw HTTP/1.1
GET /sw HTTP/1.1
[3. Proxy --> OriginServer]
GET /a-resource HTTP/1.1
Host: www.w3.org
Accept: text/xml, text/html, */*
Accept-Charset: UTF-16, iso-2022-JP
Accept-Encoding: compress, gzip
Accept-Language: ja, en
[4. OriginServer --> Proxy]
HTTP/1.1 200 OK
Content-Type: text/ charset=UTF-16
Content-Encoding: compress
Content-Language: ja
Content-Length: 1200
Vary: Content-Type, Content-Encoding, Content-Language, Content-Length
Expires: Tue, 05 Mar :00 GMT
[5. Proxy --> UserAgent]
HTTP/1.1 200 OK
Cache-control: max-age=1200, no-cache="C-Ext"
Content-Type: text/ charset=UTF-16
Content-Encoding: compress
Content-Language: ja
Content-Length: 900
Vary: C-Man, 67-Profile
Expires: Tue, 05 Mar :00 GMT
The Profile and Profile-diff headers can reveal information about the
hardware, software and user preferences to all servers which are accessed.
Especially when headers in which the user preferences is included,
implementers are strongly encouraged to let the configuration process include
a message which makes the user aware of the loss of privacy involved.
This specification allows gateways/proxies which are in between a user
agent and an origin server to add multiple CC/PP descriptions. This opens to
attacks by malicious/inadvertent gateways/proxies.
In addition, the security considerations of this specifcation are the same
as those of the HTTP Extension Framework.
Extension Framework
Composite Capability/Preference Profiles
(CC/PP): A user side framework for content negotiation
Resource Description Framework,
(RDF) Model and Syntax Specification
Resource Description Framework (RDF)
Schema Specification
: Uniform Resource Identifiers (URI): Generic Syntax
: Key words for use in RFCs to Indicate Requirement Levels
: IETF Policy on Character Sets and Languages
: The MD5 Message-Digest Algorithm
: Multipurpose Internet Mail Extensions(MIME) Part One: Format of Internet
Message Bodies
: HTTP State Management Mechanism
Real Time Streaming Protocol(RTSP)
Binary XML
Content Format Specification
for Privacy Preferences (P3P1.0) Syntax Specification Appendix 2: Fingerprints
and Canonicalization
Canonical XML}