- 1 Vapor IO Brings OpenDCRE to General Availability
- 2 VMware Takes the Wraps Off vRealize Automation and vRealize Business
- 3 Microsoft Previews Hyper-V Containers for Windows Server 2016
- 4 Mirantis Led FUEL Project Gets Installed Under OpenStack Big Tent
- 5 Red Hat Enterprise Linux 7.2 Adds Security, DR Features
HTTP Explained Page 5
Here is an example of an HTTP response from a server to a client request:
HTTP/1.0 200 OK Date: Wednesday, 02-Feb-95 23:04:12
- The server agrees to use HTTP version 1.0 for communication and sends the status 200 indicating it has successfully processed the client's request.
- It then sends the date and identifies itself as an NCSA HTTP server.
- It also indicates it is using MIME version 1.0 to describe the information it is sending, and includes the MIME-type of the information about to be sent in the "Content-type:" header.
- Finally, it sends the number of characters it is going to send, followed by a blank line and the data itself.
- Client and server headers are RFC 822 compliant mail headers. A Client may send any number of Accept: headers and the server is expected to convert the data into a form the client can accept.