MDN HTTP pages

This page lists all MDN HTTP pages along with their summary and tags.

Found 27 pages:

# Page Tags and summary
1 HTTP HTTP, Reference, Web
Editorial review completed.
2 A basic HTTP session HTTP
Because HTTP is a client-server protocol, an HTTP session consists of three phases:
3 Configuring servers for Ogg media Audio, Firefox, Firefox 3.5, Gecko, Gecko 1.9.1, HTML5, Media, Ogg, Video
Gecko 1.9.1 (Firefox 3.5) introduced support for HTML 5 audio and video media presentation without the need for the user to install any plug-ins or other software to do so. Prior to Firefox 4, Firefox supported only Ogg-encapsulated audio and video, which you may need to configure your server to support. In addition, there are several things you can do on the server side to optimize the performance of Ogg media when being presented by Firefox.
4 Content negotiation HTTP
In the Hypertext Transfer Protocol (HTTP), content negotiation is the mechanism that is used, when facing the ability to serve several equivalent contents for a given URI, to provide the best suited one to the final user. The determination of the best suited content is made through one of three mechanisms:
5 Controlling DNS prefetching DNS, HTML, HTTP
Technical review completed.
6 Firefox user agent string reference Compatibility, Firefox, Firefox 4, Gecko, Gecko 2.0, Guide
This document describes the user agent string used in Firefox 4 and later and applications based on Gecko 2.0 and later. For a breakdown of changes to the string in Gecko 2.0, see Final User Agent string for Firefox 4 (blog post). See also our document on user agent sniffing and this Hacks blog post.
7 HTTP Caching FAQ HTTP, Necko, NeedsContent
The mozilla cache holds all documents downloaded via HTTP by the user. At first this may seem odd; however, this is done to make visited documents available for back/forward, saving, viewing-as-source, etc. without requiring an additional trip to the server. It likewise improves offline browsing of cached content.
8 HTTP Pipelining FAQ Necko
HTTP/1.1 Pipelining FAQ
9 HTTP access control (CORS) AJAX, Firefox 3.5, HTTP, NeedsBrowserAgnostic, Same-origin policy, Security, XMLHttpRequest
Technical review completed.
10 HTTP cookies Cookies, HTTP
In the early days of the web, a server had no way to know if two requests came from the same web browser. This was considered as a limitation since it did not allow for instance to keep a user logged-in. This apparent limitation led Netscape to ship a technology called "cookies" in the first version of its Netscape Navigator. It has been quickly adopted by web developers and copied by other web browsers.
11 HTTP headers HTTP, Headers, Networking, Reference, headers
HTTP headers allow the client and the server to pass additional information with the request or the response. A request header consists of its case-insensitive name followed by a colon ':', then by its value (without line breaks). Leading white space before the value is ignored.
12 Cache-Control General Header, HTTP, HTTP Headers, Reference
The Cache-Control general-header field is used to specify directives for caching mechanisms in both, requests and responses. Caching directives are unidirectional, meaning that a given directive in a request is not implying that the same directive is to be given in the response.
13 Connection HTTP, Reference, Référence, Web
The Connection header controls whether or not the network connection stays open after the current transaction finishes.
14 Content-Encoding HTTP, Headers, Reference
The Content-Encoding header indicates which algorithm is been used for this message.
15 Content-Security-Policy HTTP, Property, Reference, Référence, Web, header
The Content-Security-Policy header fields allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifiying server origins and script endpoints. This helps guard against cross-site scripting attacks.
16 X-Frame-Options Gecko, HAProxy, HTTP, Response Header, Security, nginx
The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame>, <iframe> or <object> . Sites can use this to avoid clickjacking attacks, by ensuring that their content is not embedded into other sites.
17 HTTP request methods HTTP, Methods, Reference
HTTP defines a set of request methods to indicate the desired action to be performed for a given resource.
18 GET HTTP, Reference, Request method
The GET method requests a representation of the specified resource. Requests using GET should only retrieve data.
19 HTTP response status codes HTTP, Status codes
HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes: informational responses, successful responses, redirections, client errors, and servers errors.
20 100 Continue HTTP, Informational, Status code
The HTTP 100 Continue informational status response code indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished.
21 404 Not Found Client error, HTTP, Status code
The HTTP 404 Not Found client error response code indicates that a server can not find the requested resource. This response code probably is most famous one due to its frequency to occur in the web. These are often called broken or dead links and lead to link rot.
22 Index
This page lists all MDN HTTP pages along with their summary and tags.
23 Link prefetching FAQ Gecko, HTML, HTTP, Link, Necko, Performance, Prefetch, Web Development, performance
Link prefetching is a browser mechanism, which utilizes browser idle time to download or prefetch documents that the user might visit in the near future. A web page provides a set of prefetching hints to the browser, and after the browser is finished loading the page, it begins silently prefetching specified documents and stores them in its cache. When the user visits one of the prefetched documents, it can be served up quickly out of the browser's cache.
24 Protocol upgrade mechanism
The HTTP protocol provides a special mechanism allowing an already established connection to a new, incompatible, protocol. This mechanism is always client initiated, and the server may accept or refuse the switch to the new protocol.
25 Server-Side Access Control
Firefox 3.5 implements the W3C Access Control specification.  As a result, Firefox 3.5 sends specific HTTP headers for cross-site requests initiated from within XMLHttpRequest (which in Firefox 3.5 and beyond can be used to invoke different domains) and for cross-site font downloads.  It also expects to see specific HTTP headers sent back with cross-site responses.  An overview of these headers, including sample JavaScript code that initiates requests and processes responses from the server, as well as a discussion of each header, can be found here (HTTP Access Control).  The HTTP Access Control article should be read as a companion article to this one.  This article covers processing Access Control Requests and formulating Access Control Responses in PHP.  The target audience for this article are server programmers or administrators.  Although the code samples shown here are in PHP, similar concepts apply for, Perl, Python, Java, etc.; in general, these concepts can be applied to any server-side programming environment that processes HTTP requests and dynamically formulates HTTP responses.
26 data URIs Base64, Guide, Intermediate, URI, URL, url
data URIs, defined by RFC 2397, allow content creators to embed small files inline in documents.
27 www and non-www URLs URL, WWW, canonical, non-www, redirects, rel canonical, url
A recurring question among website owners is whether to choose non-www or www URLs. This page provides advice on what's best to do.

Document Tags and Contributors

 Contributors to this page: fscholz
 Last updated by: fscholz,