User:teoli

  • Revision slug: User:teoli
  • Revision title: User:teoli
  • Revision id: 55027
  • Created:
  • Creator: teoli
  • Is current revision? No
  • Comment Update on the HTTP Documentation Project; 42 words added, 3 words removed

Revision Content

 

fr
en-4
de-2
it-1
ja-0

Pense-bête.

 

 

 

 

 

 

The HTTP documentation project:

 

Page Comment Status
HTTP Main page Done. Copy-edited. Tweeted.
HTTP/Headers "Routing" page for all HTTP Headers Structure done, must be completed.
HTTP/HTTP response codes "Routing" page for all HTTP response codes Structure done, must be completed. To be renamed.
HTTP/Content  negotiation Explains the content negotiation In progress. Once finished, external links and copy-editing needed. Must tweet about it. Already now, with more content, it climbed on the first page of Google.ch with "HTTP Content Negotiation".
HTTP/Protocol upgrade mechanism Explains the usage of the Upgrade: HTTP header In progress. Once finished, external links and copy-editing needed. Must tweet about it. Needed in order to document adequately the Websocket handshake protocol 
HTTP/Quality values Explains the usage of the q values in some headers Not started. Needed to keep others pages simple. The q values are not much complex, but often poorly understood, even by browser manufacture.
HTTP/Caching Regroups everything about caching in HTTP Not started. The goal is to replace the HTTP Caching FAQ which is 1) very incomplete 2) non-encyclopedic format 3) Unclear licensing.
HTTP/Proxies Regroups everything about proxies in HTTP Not started.
HTTP/Conditional GET Speaks about the If-* HTTP headers Not started. Already spoken in the HTTP page, but I think it need some more details and examples, its own article.
HTTP/MIME types MIME Types! Not started. This is a very important article as extension are *not* the way to know the type of a resource on the internet. Though it can be moved to MIME types instead of HTTP/MIME types as it is also important to the mail message format (RFC822 and so).
HTTP/Headers/Link Explains the Link: HTTP headers Not started. The Link: header got a revival. A new RFC went out in 2010 and it is currently being extended for Firefox 7 (or Fx 8). We need to completely rewrite its documentation as the "Link Prefetching FAQ" is too specific (rel=prefetch is not the only usage), in the FAQ format rather than an encyclopedic one, is fuzzy about its license. And we have a good page for the HTML <link> element, so they must work togethe.
HTTP/Pipelining What is pipelining and how it works Must supersede the outdated HTTP Pipelining FAQ. There is a lot of work in progress in order to activate pipelining by default in Fx 8.

Revision Source

<p> </p>
<div class="ModeleBUtilisateur" style="float: left; margin: 1px; width: 238px; border: 1px solid rgb(110, 247, 167); -moz-border-radius: 0pt 0pt 0pt 0pt;">
<table border="0" cellpadding="1" cellspacing="0" style="background-color: rgb(197, 252, 220); color: rgb(0, 0, 0); -moz-border-radius: 0pt 0pt 0pt 0pt;" width="100%"> <tbody> <tr> <td align="center" class="ModeleBUtilisateurGauche" style="width: 47px; height: 47px; background-color: rgb(110, 247, 167); color: rgb(0, 0, 0); text-align: center; -moz-border-radius: 0pt 0pt 0pt 0pt;" valign="middle"> <div class="ModeleBUtilisateurImgTexte" style="font-size: 1.5em; line-height: 1.25;"><strong>fr</strong></div> </td> <td align="center" class="ModeleBUtilisateurInfo" style="padding: 1px 4px; text-align: center;" valign="middle"> <div class="ModeleBUtilisateurTexte plainlinks" style="font-size: 0.83em; line-height: 1.25;">Ma <strong>langue maternelle</strong><br> est le <strong>français</strong>.</div> </td> </tr> <tr> <td align="center" class="ModeleBUtilisateurGauche" style="width: 47px; height: 47px; background-color: rgb(119, 224, 232); color: rgb(0, 0, 0); text-align: center; -moz-border-radius: 0pt 0pt 0pt 0pt;" valign="middle"> <div class="ModeleBUtilisateurImgTexte" style="font-size: 1.5em; line-height: 1.25;"><strong>en-4</strong></div> </td> <td align="center" class="ModeleBUtilisateurInfo" style="padding: 1px 4px; text-align: center;" valign="middle"> <div class="ModeleBUtilisateurTexte plainlinks" style="font-size: 0.83em; line-height: 1.25;">This user speaks <strong>English</strong> at a <strong>near-native</strong> level.</div> </td> </tr> <tr> <td align="center" class="ModeleBUtilisateurGauche" style="width: 47px; height: 47px; background-color: rgb(153, 187, 255); color: rgb(0, 0, 0); text-align: center; -moz-border-radius: 0pt 0pt 0pt 0pt;" valign="middle"> <div class="ModeleBUtilisateurImgTexte" style="font-size: 1.5em; line-height: 1.25;"><strong>de-2</strong></div> </td> <td align="center" class="ModeleBUtilisateurInfo" style="padding: 1px 4px; text-align: center;" valign="middle"> <div class="ModeleBUtilisateurTexte plainlinks" style="font-size: 0.83em; line-height: 1.25;">Ich habe <strong>fortgeschrittene</strong> <strong>Deutschkenntnisse</strong>.</div> </td> </tr> <tr> <td align="center" class="ModeleBUtilisateurGauche" style="width: 47px; height: 47px; background-color: rgb(153, 170, 255); color: rgb(0, 0, 0); text-align: center; -moz-border-radius: 0pt 0pt 0pt 0pt;" valign="middle"> <div class="ModeleBUtilisateurImgTexte" style="font-size: 1.5em; line-height: 1.25;"><strong>it-1</strong></div> </td> <td align="center" class="ModeleBUtilisateurInfo" style="padding: 1px 4px; text-align: center;" valign="middle"> <div class="ModeleBUtilisateurTexte plainlinks" style="font-size: 0.83em; line-height: 1.25;">Posso contribuire in <strong>italiano</strong><br> con un livello <strong>semplice</strong>.</div> </td> </tr> <tr> <td align="center" class="ModeleBUtilisateurGauche" style="width: 47px; height: 47px; background-color: rgb(255, 187, 187); color: rgb(0, 0, 0); text-align: center; -moz-border-radius: 0pt 0pt 0pt 0pt;" valign="middle"> <div class="ModeleBUtilisateurImgTexte" style="font-size: 1.5em; line-height: 1.25;"><strong>ja-0</strong></div> </td> <td align="center" class="ModeleBUtilisateurInfo" style="padding: 1px 4px; text-align: center;" valign="middle"> <div class="ModeleBUtilisateurTexte plainlinks" style="font-size: 0.83em; line-height: 1.25;">この利用者は<strong>日本語</strong>が<strong>わかりません</strong>(または理解するのがかなり困難です)。</div> </td> </tr> </tbody>
</table>
</div>
<p><a href="/User:teoli/Notes" title="User:teoli/Notes">Pense-bête</a>.</p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<p> </p>
<h4>The HTTP documentation project:</h4>
<p> </p>
<table class="compat-table"> <tbody> <tr> <th>Page</th> <th>Comment</th> <th>Status</th> </tr> <tr> <td><a href="/en/HTTP" title="https://developer.mozilla.org/en/HTTP">HTTP</a></td> <td>Main page</td> <td><span style="color: rgb(0, 255, 0);">Done. Copy-edited. Tweeted.<br> </span></td> </tr> <tr> <td><a href="/en/HTTP/Headers" title="https://developer.mozilla.org/en/HTTP/Headers">HTTP/Headers</a></td> <td>"Routing" page for all HTTP Headers</td> <td><span style="color: rgb(0, 255, 0);">Structure done</span>, <span style="color: rgb(255, 0, 0);">must be completed.</span></td> </tr> <tr> <td><a href="/en/HTTP/HTTP_response_codes" title="https://developer.mozilla.org/en/HTTP/HTTP_response_codes">HTTP/HTTP response codes</a></td> <td>"Routing" page for all HTTP response codes</td> <td><span style="color: rgb(0, 255, 0);">Structure done</span>, <span style="color: rgb(255, 0, 0);">must be completed. To be renamed.</span></td> </tr> <tr> <td><a href="/en/HTTP/Content_negotiation" title="https://developer.mozilla.org/en/HTTP/Content_negotiation">HTTP/Content  negotiation</a></td> <td>Explains the content negotiation</td> <td><span style="color: rgb(255, 153, 0);">In progress.<span style="color: rgb(255, 0, 0);"> Once finished, external links and copy-editing needed. Must tweet about it. </span><span style="color: rgb(0, 0, 0);">Already now, with more content, it climbed on the first page of Google.ch with "HTTP Content Negotiation".</span><br> </span></td> </tr> <tr> <td><a href="/en/HTTP/Protocol_upgrade_mechanism" title="https://developer.mozilla.org/en/HTTP/Protocol_upgrade_mechanism">HTTP/Protocol upgrade mechanism</a></td> <td>Explains the usage of the <code>Upgrade: </code>HTTP header</td> <td><span style="color: rgb(255, 153, 0);">In progress.<span style="color: rgb(255, 0, 0);"> Once finished, external links and copy-editing needed. Must tweet about it. </span></span><span style="color: rgb(255, 153, 0);"><span style="color: rgb(0, 0, 0);">Needed in order to document adequately the Websocket handshake protocol  </span></span></td> </tr> <tr> <td>HTTP/Quality values</td> <td>Explains the usage of the q values in some headers</td> <td><span style="color: rgb(255, 0, 0);">Not started.</span> Needed to keep others pages simple. The q values are not much complex, but often poorly understood, even by browser manufacture.</td> </tr> <tr> <td>HTTP/Caching</td> <td>Regroups everything about caching in HTTP</td> <td><span style="color: rgb(255, 0, 0);">Not started.</span> The goal is to replace the <a href="/en/HTTP_Caching_FAQ" title="https://developer.mozilla.org/en/HTTP_Caching_FAQ">HTTP Caching FAQ</a> which is 1) very incomplete 2) non-encyclopedic format 3) Unclear licensing.</td> </tr> <tr> <td>HTTP/Proxies</td> <td>Regroups everything about proxies in HTTP</td> <td><span style="color: rgb(255, 0, 0);">Not started.</span></td> </tr> <tr> <td>HTTP/Conditional GET</td> <td>Speaks about the <code>If-*</code> HTTP headers</td> <td><span style="color: rgb(255, 0, 0);">Not started. </span>Already spoken in the HTTP page, but I think it need some more details and examples, its own article.</td> </tr> <tr> <td>HTTP/MIME types</td> <td>MIME Types!</td> <td><span style="color: rgb(255, 0, 0);">Not started. </span>This is a very important article as extension are *not* the way to know the type of a resource on the internet. Though it can be moved to MIME types instead of HTTP/MIME types as it is also important to the mail message format (RFC822 and so).</td> </tr> <tr> <td>HTTP/Headers/Link</td> <td>Explains the <code>Link: </code>HTTP headers</td> <td><span style="color: rgb(255, 0, 0);">Not started. </span>The <code>Link:</code> header got a revival. A new RFC went out in 2010 and it is currently being extended for Firefox 7 (or Fx 8). We need to completely rewrite its documentation as the "<a href="/en/Link_prefetching_FAQ" title="https://developer.mozilla.org/en/Link_prefetching_FAQ">Link Prefetching FAQ</a>" is too specific (<code>rel=prefetch</code> is not the only usage), in the FAQ format rather than an encyclopedic one, is fuzzy about its license. And we have a good page for the HTML <a href="/en/HTML/Element/link" title="https://developer.mozilla.org/en/HTML/Element/link"><code>&lt;link&gt;</code></a> element, so they must work togethe.</td> </tr> <tr> <td>HTTP/Pipelining</td> <td>What is pipelining and how it works</td> <td>Must supersede the outdated <a href="/en/HTTP_Pipelining_FAQ" title="https://developer.mozilla.org/en/HTTP_Pipelining_FAQ">HTTP Pipelining FAQ</a>. There is a lot of work in progress in order to activate pipelining by default in Fx 8.</td> </tr> </tbody>
</table>
Revert to this revision