aboutsummaryrefslogtreecommitdiff
path: root/files/es/web/http/recursos_y_especificaciones/index.html
blob: 0c36d6e3e62f3dcb254c3781d4e42dc7cae2e37b (plain)
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
---
title: Recursos y especificaciones de HTTP
slug: Web/HTTP/recursos_y_especificaciones
translation_of: Web/HTTP/Resources_and_specifications
---
<div>{{HTTPSidebar}}</div>

<p>HTTP se especificó por primera vez a principios de los 90s. Diseñado con extensibilidad en mente, ha visto numerosas adiciones a lo largo de los años; esto lleva a que su especificación se disemine a través de númerosos documentos (en medio de extensiones experimentales abandonadas). Esta página presenta una lista de los recursos relevantes sobre HTTP:</p>

<table class="standard-table">
 <thead>
  <tr>
   <th scope="col">Specification</th>
   <th scope="col">Title</th>
   <th scope="col">Status</th>
  </tr>
 </thead>
 <tbody>
  <tr>
   <td>{{rfc(7230)}}</td>
   <td>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7231)}}</td>
   <td>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7232)}}</td>
   <td>Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7233)}}</td>
   <td>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7234)}}</td>
   <td>Hypertext Transfer Protocol (HTTP/1.1): Caching</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(5861)}}</td>
   <td>HTTP Cache-Control Extensions for Stale Content</td>
   <td>Informational</td>
  </tr>
  <tr>
   <td>{{rfc(8246)}}</td>
   <td>HTTP Immutable Responses</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7235)}}</td>
   <td>Hypertext Transfer Protocol (HTTP/1.1): Authentication</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(6265)}}</td>
   <td>HTTP State Management Mechanism<br>
    <em>Defines Cookies</em></td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td><a href="https://tools.ietf.org/html/draft-ietf-httpbis-cookie-prefixes-00">Draft spec</a></td>
   <td>Cookie Prefixes</td>
   <td>IETF Draft</td>
  </tr>
  <tr>
   <td><a href="https://tools.ietf.org/html/draft-ietf-httpbis-cookie-same-site-00">Draft spec</a></td>
   <td>Same-Site Cookies</td>
   <td>IETF Draft</td>
  </tr>
  <tr>
   <td><a href="https://tools.ietf.org/html/draft-ietf-httpbis-cookie-alone-01">Draft spec</a></td>
   <td>Deprecate modification of 'secure' cookies from non-secure origins</td>
   <td>IETF Draft</td>
  </tr>
  <tr>
   <td>{{rfc(2145)}}</td>
   <td>Use and Interpretation of HTTP Version Numbers</td>
   <td>Informational</td>
  </tr>
  <tr>
   <td>{{rfc(6585)}}</td>
   <td>Additional HTTP Status Codes</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7538)}}</td>
   <td>The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7725)}}</td>
   <td>An HTTP Status Code to Report Legal Obstacles</td>
   <td>On the standard track</td>
  </tr>
  <tr>
   <td>{{rfc(2397)}}</td>
   <td>The "data" URL scheme</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(3986)}}</td>
   <td>Uniform Resource Identifier (URI): Generic Syntax</td>
   <td>Internet Standard</td>
  </tr>
  <tr>
   <td>{{rfc(5988)}}</td>
   <td>Web Linking<br>
    <em>Defines the {{HTTPHeader("Link")}} header</em></td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td><a href="https://tools.ietf.org/id/draft-thomson-hybi-http-timeout-01.html">Experimental spec</a></td>
   <td>Hypertext Transfer Protocol (HTTP) Keep-Alive Header</td>
   <td>Informational (Expired)</td>
  </tr>
  <tr>
   <td><a href="http://httpwg.org/http-extensions/client-hints.html">Draft spec</a></td>
   <td>HTTP Client Hints</td>
   <td>IETF Draft</td>
  </tr>
  <tr>
   <td>{{rfc(7578)}}</td>
   <td>Returning Values from Forms: multipart/form-data</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(6266)}}</td>
   <td>Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(2183)}}</td>
   <td>Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field<br>
    <em>Only a subset of syntax of the {{HTTPHeader("Content-Disposition")}} header can be used in the context of HTTP messages.</em></td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7239)}}</td>
   <td>Forwarded HTTP Extension</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(6455)}}</td>
   <td>The WebSocket Protocol</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(5246)}}</td>
   <td>The Transport Layer Security (TLS) Protocol Version 1.2<br>
    <em>This specification has been modified by subsequent RFCs, but these modifications have no effect on the HTTP protocol.</em></td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td><a href="https://tlswg.github.io/tls13-spec/)">Draft spec</a></td>
   <td>The Transport Layer Security (TLS) Protocol Version 1.3<br>
    <em>Once ready, this protocol will supersede TLS 1.2.</em></td>
   <td>IETF Draft</td>
  </tr>
  <tr>
   <td>{{rfc(2817)}}</td>
   <td>Upgrading to TLS Within HTTP/1.1</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7540)}}</td>
   <td>Hypertext Transfer Protocol Version 2 (HTTP/2)</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(7541)}}</td>
   <td>HPACK: Header Compression for HTTP/2</td>
   <td>On the standard track</td>
  </tr>
  <tr>
   <td>{{rfc(7838)}}</td>
   <td>HTTP Alternative Services</td>
   <td>On the standard track</td>
  </tr>
  <tr>
   <td>{{rfc(7301)}}</td>
   <td>Transport Layer Security (TLS) Application-Layer Protocol Negotiation Extension<br>
    <em>Used to negotiate HTTP/2 at the transport to save an extra request/response round trip.</em></td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(6454)}}</td>
   <td>The Web Origin Concept</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{SpecName('Fetch', '#cors-protocol', 'CORS')}}</td>
   <td>Cross-Origin Resource Sharing</td>
   <td>{{Spec2("Fetch")}}</td>
  </tr>
  <tr>
   <td>{{rfc(7034)}}</td>
   <td>HTTP Header Field X-Frame-Options</td>
   <td>Informational</td>
  </tr>
  <tr>
   <td>{{rfc(6797)}}</td>
   <td>HTTP Strict Transport Security (HSTS)</td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{SpecName("Upgrade Insecure Requests")}}</td>
   <td>Upgrade Insecure Requests</td>
   <td>{{Spec2("Upgrade Insecure Requests")}}</td>
  </tr>
  <tr>
   <td>{{SpecName("CSP 1.0")}}</td>
   <td>Content Security Policy 1.0<br>
    <em>CSP 1.1 and CSP 3.0 doesn't extend the HTTP standard</em></td>
   <td>{{Spec2("CSP 1.0")}}</td>
  </tr>
  <tr>
   <td><a href="https://msdn.microsoft.com/en-us/library/jj676915(v=vs.85).aspx">Microsoft document</a></td>
   <td>Specifying legacy document modes*<br>
    <em>Defines X-UA-Compatible</em></td>
   <td>Note</td>
  </tr>
  <tr>
   <td>{{rfc(5689)}}</td>
   <td>HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)<br>
    <em>These extensions of the Web, as well as CardDAV and CalDAV, are out-of-scope for HTTP on the Web. Modern APIs for application are defines using the RESTful pattern nowadays.</em></td>
   <td>Proposed Standard</td>
  </tr>
  <tr>
   <td>{{rfc(2324)}}</td>
   <td>Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</td>
   <td>April 1st joke spec</td>
  </tr>
  <tr>
   <td>{{rfc(7168)}}</td>
   <td>The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)</td>
   <td>April 1st joke spec</td>
  </tr>
  <tr>
   <td>{{SpecName("HTML WHATWG")}}</td>
   <td>HTML<br>
    <em>Defines extensions of HTTP for Server-Sent Events</em></td>
   <td>{{Spec2("HTML WHATWG")}}</td>
  </tr>
  <tr>
   <td><a href="https://www.w3.org/2011/tracking-protection/drafts/tracking-dnt.html">Tracking Preference Expression</a></td>
   <td>DNT header</td>
   <td>Editor's draft / Candidate recommendation</td>
  </tr>
  <tr>
   <td><a href="http://wicg.github.io/reporting/">Reporting API</a></td>
   <td><code>Report-To</code> header</td>
   <td>Draft</td>
  </tr>
 </tbody>
</table>

<p> </p>