||Done. Copy-edited. Tweeted.
||"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.
||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
||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.
||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.
||Regroups everything about proxies in HTTP
||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.
||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).
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.
||What is pipelining and how it works
||Not started. 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.
||All about Cookies, Set-Cookie, Set-Cookie2