http
24.3 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><!-- Generated from data/head.php, ../../smarty/{head.tpl} --><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>HTTP Current Status - W3C</title><link rel="stylesheet" href="/2008/site/css/minimum" type="text/css" media="handheld, all" /><style type="text/css" media="print, screen and (min-width: 481px)" xml:space="preserve">
@import url("/2008/site/css/advanced");
</style><link href="/2008/site/css/minimum" rel="stylesheet" type="text/css" media="handheld, only screen and (max-device-width: 480px)" /><meta name="viewport" content="width=device-width" /><link rel="stylesheet" href="/2008/site/css/print" type="text/css" media="print" /><link rel="shortcut icon" href="/2008/site/images/favicon.ico" type="image/x-icon" /></head><body id="www-w3-org" class="w3c_public"><div id="w3c_container">
<!-- Generated from data/mast.php, ../../smarty/{mast.tpl} -->
<div id="w3c_mast">
<!-- #w3c_mast / Page top header -->
<h1 class="logo">
<a tabindex="2" accesskey="1" href="/"><img src="/2008/site/images/logo-w3c-mobile-lg" width="90" height="53" alt="W3C" /></a>
<span class="alt-logo">W3C</span>
</h1>
<div id="w3c_nav">
<!-- Search form and media selection -->
<form action="/Help/search" method="get" enctype="application/x-www-form-urlencoded"><div class="w3c_sec_nav"><!-- --></div><ul class="main_nav"><li class="first-item">
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li><li class="search-item">
<div id="search-form">
<input tabindex="3" class="text" name="q" value="" title="Search" type="text" />
<button id="search-submit" name="search-submit" type="submit"><img class="submit" src="/2008/site/images/search-button" alt="Search" width="21" height="17" /></button>
</div>
</li></ul></form>
</div>
<!-- /end #w3c_nav -->
</div>
<!-- /end #w3c_mast -->
<div id="w3c_main">
<!-- Generated from data/crumbs.php, ../../smarty/{crumbs.tpl} -->
<div id="w3c_logo_shadow" class="w3c_leftCol">
<img height="32" alt="" src="/2008/site/images/logo-shadow" />
</div>
<div class="w3c_leftCol"><h2 class="offscreen">Site Navigation</h2>
<br /></div>
<div class="w3c_mainCol">
<div id="w3c_crumbs">
<div id="w3c_crumbs_frame">
<ul class="bct"> <!-- .bct / Breadcrumbs -->
<li class="skip"><a tabindex="1" accesskey="2" title="Skip to content (e.g., when browsing via audio)" href="#w3c_content_body">Skip</a></li>
<li><a href="/">W3C</a> <span class="cr">»</span> </li>
<li><a href="/standards/">Standards</a> <span class="cr">»</span> </li>
<li><a href="/TR/">All Standards and Drafts</a> <span class="cr">»</span> </li>
<li class="current">HTTP Current Status</li>
</ul>
</div>
</div>
<h1 class="title">HTTP Current Status</h1>
<ul class="w3c_toc">
<li>
<a href="#drafts">drafts</a>
<span class="bullet">• </span>
</li>
<li>
<a href="#obsolete">obsolete specifications</a>
<span class="bullet">• </span>
</li>
<li>
<a href="#externalrefs">resources developed outside W3C</a>
</li>
</ul>
<div id="w3c_content_body">
<div id="w3c_generated_status">
<p id="w3c_toggle_include" class="default_open intro tPadding">This page summarizes the relationships among specifications, whether they are finished standards or drafts. Below, each title
links to the most recent version of a document.
For related introductory information, see: <a href="http://www.w3.org/standards/webdesign/privacy">Privacy</a>, <a href="http://www.w3.org/standards/webarch/protocols">Protocols</a>, <a href="http://www.w3.org/standards/webofservices/protocols">Protocols</a>.</p>
<h2 id="drafts">Drafts</h2>
<p>Below are draft documents:
<a href="/2005/10/Process-20051014/tr.html#RecsWD">other Working Drafts</a>.
Some of these may become Web Standards through the <a href="/Consortium/Process/tr#rec-advance">W3C Recommendation Track
process</a>. Others may be published as Group Notes or
become obsolete specifications.</p>
<h3 id="wd">Other Working Drafts</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/tracking-dnt" title="Tracking Preference Expression (DNT) publication history">2011-11-14</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-tracking-dnt-20111114/">Tracking Preference Expression (DNT)</a>
</h4>
<div class="expand_description">
<p>This specification defines the technical mechanisms for expressing a cross-site tracking preference and mechanisms for sites to signal whether and how they honor this preference.
</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/tracking-compliance" title="Tracking Compliance and Scope publication history">2011-11-14</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-tracking-compliance-20111114/">Tracking Compliance and Scope</a>
</h4>
<div class="expand_description">
<p>This specification defines the meaning of a Do Not Track preference and sets out practices for websites to comply with this preference.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/eventsource" title="Server-Sent Events publication history">2011-10-20</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-eventsource-20111020/">Server-Sent Events</a>
</h4>
<div class="expand_description">
<p>This specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/HTTP-in-RDF10" title="HTTP Vocabulary in RDF 1.0 publication history">2011-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-HTTP-in-RDF10-20110510/">HTTP Vocabulary in RDF 1.0</a>
</h4>
<div class="expand_description">
<p>The identification of resources on the Web by <acronym>URI</acronym> alone may not be sufficient, as other factors such as <acronym>HTTP</acronym> content negotiation might come into play. This issue is particularly significant for quality assurance testing, conformance claims, and reporting languages like the W3C Evaluation And Report Language (EARL). This document provides a representation of the HTTP vocabulary in <acronym>RDF</acronym>, to allow quality assurance tools to record the HTTP headers that have been exchanged between a client and a server. The RDF terms defined by this document represent the core HTTP specification defined by <acronym>RFC</acronym> 2616, as well as additional HTTP headers registered by <acronym>IANA</acronym>. These terms can also be used to record <acronym>HTTPS</acronym> exchanges.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/Content-in-RDF10" title="Representing Content in RDF 1.0 publication history">2011-05-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is WD" href="http://www.w3.org/TR/2011/WD-Content-in-RDF10-20110510/">Representing Content in RDF 1.0</a>
</h4>
<div class="expand_description">
<p>This document is a specification for a vocabulary to represent Content in <acronym>RDF</acronym>. This vocabulary is intended to provide a flexible framework within different usage scenarios to semantically represent any type of content, be it on the Web or in local storage media. For example, it can be used by Web accessibility evaluation tools to record a representation of the assessed Web content in an Evaluation And Report Language (EARL) 1.0 Schema evaluation report. The document contains introductory information on its usage and some examples.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
<h2 id="obsolete">Obsolete Specifications</h2>
<p>These specifications have either been superseded by others,
or have been abandoned. They remain available for archival
purposes, but are not intended to be used.</p>
<h3 id="retired">
Retired
</h3>
<div class="data lMargin rMargin">
<table class="w3c_spec_summary_table">
<tbody>
<tr>
<td class="table_datecol">
<a href="../history/WD-HTTP-NG-interfaces" title="HTTP-ng Web Interfaces publication history">1998-07-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/1998/WD-HTTP-NG-interfaces-19980710">HTTP-ng Web Interfaces</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WD-HTTP-NG-architecture" title="HTTP-ng Architectural Model publication history">1998-07-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/1998/WD-HTTP-NG-architecture-19980710">HTTP-ng Architectural Model</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WD-HTTP-NG-wire" title="HTTP-ng Binary Wire Protocol publication history">1998-07-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/1998/WD-HTTP-NG-wire-19980710">HTTP-ng Binary Wire Protocol</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WD-mux" title="SMUX Protocol Specification publication history">1998-07-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/1998/WD-mux-19980710">SMUX Protocol Specification</a>
</h4>
<div class="expand_description">
<p>This document defines the experimental multiplexing protocol
referred to as "SMUX". SMUX is a session management protocol
separating the underlying transport from the upper level
application protocols. It provides a lightweight communication
channel to the application layer by multiplexing data streams on
top of a reliable stream oriented transport. By supporting
coexistence of multiple application level protocols (e.g. HTTP and
HTTP/NG), SMUX should ease transitions to future Web protocols, and
communications of client applets using private protocols with
servers over the same TCP connection as the HTTP conversation.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/NOTE-HTTP-NG-testbed" title="Design of HTTP-ng Testbed publication history">1998-07-10</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/1998/NOTE-HTTP-NG-testbed-19980710">Design of HTTP-ng Testbed</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WD-HTTP-NG-goals" title="Short- and Long-Term Goals for the HTTP-NG Project publication history">1998-03-27</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/1998/WD-HTTP-NG-goals-19980327">Short- and Long-Term Goals for the HTTP-NG Project</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WD-http-pep" title="PEP Specification: an Extension Mechanism for HTTP publication history">1997-11-21</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/WD-http-pep-971121">PEP Specification: an Extension Mechanism for HTTP</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr>
<td>
<a href="../history/WD-jepi-uppflow" title="Selecting Payment Mechanisms Over HTTP publication history">1997-01-06</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/WD-jepi-uppflow-970106">Selecting Payment Mechanisms Over HTTP</a>
</h4>
<div class="expand_description">
<p>This is a sample short description for this specification;
over time we will replace this description with a real one.</p>
</div>
</td>
</tr>
<tr class="lastRow">
<td>
<a href="../history/WD-ilu-requestor" title="The ILU Requester: Object Services in HTTP Servers publication history">1996-03-07</a>
</td>
<td>
<h4 class="w3c_status_title">
<a title="status is RETIRED" href="http://www.w3.org/TR/WD-ilu-requestor-960307">The ILU Requester: Object Services in HTTP Servers</a>
</h4>
<div class="expand_description">
<p>The Common Gateway
Interface (CGI) is not scaling to meet the requirements of
today's dynamic, interactive webs. For this reason, multiple
vendors have proposed C callable APIs. These APIs allow authors to
alleviate the performance penalty of CGI, and allow tighter
integration of add-in modules. Unfortunately, this comes at the
price of complexity and portability.</p>
<p>This document describes a new model for extending WWW servers.
First, HTTP is captured using an interface
specification, which eliminates the ambiguities of
interpretating a standards-track document. This interface is then
implemented atop a particular httpd's API. Finally, all of this is
done using a standard distributed object model called ILU.</p>
<p>Digital Creations' work on our ILU
Requester reflects this design and shows its advantages.
This paper describes the ILU Requester.</p>
</div>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
<div id="externalrefs" class="tMarginLg">
<h2>Resources Developed Outside W3C</h2>
<p>The following resources are relevant to this area of work.</p>
<h3>HTTPbis</h3>
<p><strong>2009-11-26</strong>: draft -08 of the <a href="http://tools.ietf.org/wg/httpbis/">revised HTTP/1.1</a> specifications (See <a href="#http">HTTP/1.1 (RFC 2616) below</a>)</p>
<ul>
<li><a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p1-messaging-08.txt">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a></li>
<li><a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p2-semantics-08.txt">HTTP/1.1, part 2: Message Semantics</a></li>
<li><a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p3-payload-08.txt">HTTP/1.1, part 3: Message Payload and Content Negotiation</a></li>
<li><a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p4-conditional-08.txt">HTTP/1.1, part 4: Conditional Requests</a></li>
<li><a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p5-range-08.txt">HTTP/1.1, part 5: Range Requests and Partial Responses</a></li>
<li><a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p6-cache-08.txt">HTTP/1.1, part 6: Caching
</a></li>
<li><a href="http://www.ietf.org/internet-drafts/draft-ietf-httpbis-p7-auth-07.txt">HTTP/1.1, part 7: Authentication</a></li>
</ul>
<h3>HTTP State</h3>
<p>See <a href="http://www.ietf.org/">IETF</a>'s <a href="http://tools.ietf.org/wg/httpstate/">HTTPState</a> Working Group page.</p>
<h3>BiDirectional or Server-Initiated HTTP</h3>
<p>See <a href="http://www.ietf.org">IETF</a>'s <a href="http://tools.ietf.org/wg/hybi/">BiDirectional or Server-Initiated HTTP</a> Working Group page.</p>
<h3 id="http">RFC 2616</h3>
<p>
<a href="http://www.ietf.org/rfc/rfc2616.txt">RFC 2616: Hypertext Transfer Protocol -- HTTP/1.1</a> describe the HTTP 1.1 protocol. Quoting from the RFC: " The Hypertext Transfer Protocol (HTTP) is an application-level
protocol for distributed, collaborative, hypermedia information
systems. It is a generic, stateless, protocol which can be used for
many tasks beyond its use for hypertext, such as name servers and
distributed object management systems, through extension of its
request methods, error codes and headers."</p>
<h3>RFC 1945</h3>
<p>
<a href="http://www.ietf.org/rfc/rfc1945.txt">RFC 1945: Hypertext Transfer Protocol -- HTTP/1.0</a> describes the common usage of
the HTTP protocol in the early years of the Web.</p>
<h3>HTTP 0.9</h3>
<p>
<a href="http://www.w3.org/Protocols/HTTP/AsImplemented.html">
<cite> The Original HTTP as defined in 1991 </cite>
</a> is the historical documentation of the first definition of the HTTP protocol.</p>
</div>
</div>
</div>
</div><!-- Generated from data/footer.php, ../../smarty/{footer-block.tpl} --><div id="w3c_footer">
<div id="w3c_footer-inner">
<h2 class="offscreen">Footer Navigation</h2>
<div class="w3c_footer-nav">
<h3>Navigation</h3>
<ul class="footer_top_nav"><li>
<a href="/">Home</a>
</li><li>
<a href="/standards/">Standards</a>
</li><li>
<a href="/participate/">Participate</a>
</li><li>
<a href="/Consortium/membership">Membership</a>
</li><li class="last-item">
<a href="/Consortium/">About W3C</a>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>Contact W3C</h3>
<ul class="footer_bottom_nav"><li>
<a href="/Consortium/contact">Contact</a>
</li><li>
<a accesskey="0" href="/Help/">Help and FAQ</a>
</li><li>
<a href="/Consortium/sponsor/">Sponsor / Donate</a>
</li><li>
<a href="/Consortium/siteindex">Site Map</a>
</li><li>
<address id="w3c_signature">
<a href="mailto:site-comments@w3.org">Feedback</a> (<a href="http://lists.w3.org/Archives/Public/site-comments/">archive</a>)</address>
</li></ul>
</div>
<div class="w3c_footer-nav">
<h3>W3C Updates</h3>
<ul class="footer_follow_nav"><li>
<a href="http://twitter.com/W3C" title="Follow W3C on Twitter">
<img src="/2008/site/images/twitter-bird" alt="Twitter" width="78" height="83" class="social-icon" />
</a>
<a href="http://identi.ca/w3c" title="See W3C on Identica">
<img src="/2008/site/images/identica-logo" alt="Identica" width="91" height="83" class="social-icon" />
</a>
</li></ul>
</div>
<p class="copyright">Copyright © 2012 W3C <sup>®</sup> (<a href="http://www.csail.mit.edu/">
<acronym title="Massachusetts Institute of Technology">MIT</acronym>
</a>, <a href="http://www.ercim.eu/">
<acronym title="European Research Consortium for Informatics and Mathematics"> ERCIM</acronym>
</a>, <a href="http://www.keio.ac.jp/">Keio</a>) <a href="/Consortium/Legal/ipr-notice">Usage policies apply</a>.</p>
</div>
</div><!-- /end #footer --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><!-- Generated from data/scripts.php, ../../smarty/{scripts.tpl} --><!-- At the bottom for performance reasons --><div id="w3c_scripts">
<script type="text/javascript" src="/2008/site/js/main" xml:space="preserve"><!-- --></script>
</div></body></html>