HTTP

The 404 or Not Found error message is an HTTP standard response code indicating that the client was able to communicate with the server, but the server either could not find the file that was requested, or was unwilling to fulfill the request for it and did not wish to reveal the reason why. ...more on Wikipedia about "404 error"

In the context of an HTTP transaction, the basic authentication scheme is a method designed to allow a web browser, or other client program, to provide credentials – in the form of a user name and password – when making a request. Although the scheme is easily implemented, it relies on the assumption that the connection between the client and server computers is secure and can be trusted. Specifically, the credentials are passed as plaintext and could be intercepted easily. The scheme also provides no protection for the information passed back from the server. ...more on Wikipedia about "Basic authentication scheme"

Content negotiation is a mechanism defined in the HTTP specification that makes it possible to serve different versions of a document (or more generally, a resource) at the same URL, so that user agents can choose which version fit their capabilities the best. One of the most classical uses of this mechanism is to serve an image as both GIF and PNG, so that a browser that doesn't understand PNG can still display the GIF version. To summarize how this works, it's enough to say that user agents are supposed to send an HTTP header (Accept) with the various MIME types they understand and with indications of how well they understand it. Then, the server replies with the version of the resource that fits the user agents' needs. ...more on Wikipedia about "Content negotiation"

Digest access authentication is one of the agreed methods a web page can use to negotiate credentials with a web user (using the HTTP protocol). This method builds upon (and obsoletes) the basic authentication scheme, allowing user identity to be established without having to send a password in plaintext over the network. ...more on Wikipedia about "Digest access authentication"

An HTTP cookie is a packet of information sent by a server to a World Wide Web browser and then sent back by the browser each time it accesses that server. Cookies are used for user authentication, user tracing, and maintaining user-specific information (preferences, electronic shopping cart, etc.) ...more on Wikipedia about "HTTP cookie"

HTTP pipelining appeared in HTTP/1.1. It allows clients to send multiple requests at once, without waiting for an answer. Servers can also send multiple answers without closing their socket. This results in fewer roundtrips and faster load times. This is particularly useful for satellite Internet connections and other connections with high latency as separate requests need not be made for each file. ...more on Wikipedia about "HTTP pipelining"

HTTP-Tunnel technology allows users to perform various Internet tasks despite the restrictions imposed by firewalls. This is made possible by sending data through HTTP (port 80). Additionally, HTTP-Tunnel technology is very secure, making it indispensable for both average and business communications. ...more on Wikipedia about "HTTP-Tunnel"

HyperText Transfer Protocol (HTTP) is the primary method used to transfer or convey information on the World Wide Web. The original purpose was to provide a way to publish and receive HTML pages. ...more on Wikipedia about "HyperText Transfer Protocol"

==Status codes== ...more on Wikipedia about "List of HTTP status codes"

Secure hypertext transfer protocol (S-HTTP) is an alternative mechanism to the https: URI scheme for encrypting web communications carried over HTTP. S-HTTP is defined in RFC 2660. ...more on Wikipedia about "Secure hypertext transfer protocol"

XMLHTTP is a set of APIs that can be used by JavaScript, JScript, VBScript and other web browser scripting languages to transfer and manipulate XML data to and from a web server using HTTP, establishing an independent connection channel between Client-Side and Server-Side. ...more on Wikipedia about "XMLHTTP"

This article is licensed under the GNU Free Documentation License.
It uses material from the Wikipedia . Direct links to the original articles are in the text.
If you use exact copy or modified of this article you should preserve above paragraph and put also : It uses material from the Shortopedia article about "HTTP".

MAIN PAGE

MAIN INDEX

CONTACT US