In Introduction To HTTP Basics

11/13/2015
InIntroductiontoHTTPBasics
yet another insignificant programming notes... | HOME
HTTP (HyperText Transfer Protocol)

Basics
Introduction
The WEB
Internet or The Web is a massive distributed client/server information system as depicted in the following diagram.
Many applications are running concurrently over the Web, such as web browsing/surfing, email, file transfer, audio & video streaming, and so on. In order
for proper communication to take place between the client and the server, these applications must agree on a specific applicationlevel protocol such as
HTTP, FTP, SMTP, POP, and etc.
HyperText Transfer Protocol HTTP

HTTP Hypertext Transfer Protocol is perhaps the most popular application protocol used in the Internet or The WEB.
HTTP is an asymmetric requestresponse clientserver protocol as illustrated. An HTTP client sends a request message to an HTTP server. The server, in
turn, returns a response message. In other words, HTTP is a pull protocol, the client pulls information from the server instead of server pushes
information down to the client.
HTTP is a stateless protocol. In other words, the current request does not know what has been done in the previous requests.
HTTP permits negotiating of data type and representation, so as to allow systems to be built independently of the data being transferred.
Quoting from the RFC2616: "The Hypertext Transfer Protocol HTTP is an applicationlevel protocol for distributed, collaborative, hypermedia
information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and
distributed object management systems, through extension of its request methods, error codes and headers."
Browser
Whenever you issue a URL from your browser to get a web resource using HTTP, e.g. http://www.test101.com/index.html, the browser turns the URL
into a request message and sends it to the HTTP server. The HTTP server interprets the request message, and returns you an appropriate response message,
https://www3.ntu.edu.sg/home/ehchua/programming/webprogramming/HTTP_Basics.html
1/21
11/13/2015
which is either the resource you requested or an error message. This process is illustrated below:
Uniform Resource Locator URL

A URL Uniform Resource Locator is used to uniquely identify a resource over the web. URL has the following syntax:
protocol://hostname:port/pathandfilename
There are 4 parts in a URL:

1. Protocol: The applicationlevel protocol used by the client and server, e.g., HTTP, FTP, and telnet.
2. Hostname: The DNS domain name e.g., www.test101.com or IP address e.g., 192.128.1.2 of the server.
3. Port: The TCP port number that the server is listening for incoming requests from the clients.
4. Pathandfilename: The name and location of the requested resource, under the server document base directory.
For example, in the URL http://www.test101.com/docs/index.html, the communication protocol is HTTP; the hostname is www.test101.com. The port
number was not specified in the URL, and takes on the default number, which is TCP port 80 for HTTP. The path and file name for the resource to be located
is "/docs/index.html".
Other examples of URL are:
ftp://www.ftp.org/docs/test.txt
mailto:user@test101.com
news:soc.culture.Singapore
telnet://www.test101.com/
HTTP Protocol
As mentioned, whenever you enter a URL in the address box of the browser, the browser translates the URL into a request message according to the
specified protocol; and sends the request message to the server.
For example, the browser translated the URL http://www.test101.com/doc/index.html into the following request message:
GET/docs/index.htmlHTTP/1.1
Host:www.test101.com
Accept:image/gif,image/jpeg,*/*
AcceptLanguage:enus
AcceptEncoding:gzip,deflate
UserAgent:Mozilla/4.0(compatible;MSIE6.0;WindowsNT5.1)
(blankline)
When this request message reaches the server, the server can take either one of these actions:
1. The server interprets the request received, maps the request into a file under the server's document directory, and returns the file requested to the
client.
2. The server interprets the request received, maps the request into a program kept in the server, executes the program, and returns the output of the
program to the client.
3. The request cannot be satisfied, the server returns an error message.
An example of the HTTP response message is as shown:
HTTP/1.1200OK
Date:Sun,18Oct200908:56:53GMT
Server:Apache/2.2.14(Win32)
LastModified:Sat,20Nov200407:16:26GMT
ETag:"10000000565a52c3e94b66c2e680"
AcceptRanges:bytes
ContentLength:44
Connection:close
ContentType:text/html
XPad:avoidbrowserbug
<html><body><h1>Itworks!</h1></body></html>
2/21
11/13/2015
The browser receives the response message, interprets the message and displays the contents of the message on the browser's window according to the
media type of the response as in the ContentType response header. Common media type include "text/plain", "text/html", "image/gif",
"image/jpeg", "audio/mpeg", "video/mpeg", "application/msword", and "application/pdf".
In its idling state, an HTTP server does nothing but listening to the IP addresses and ports specified in the configuration for incoming request. When a
request arrives, the server analyzes the message header, applies rules specified in the configuration, and takes the appropriate action. The webmaster's main
control over the action of web server is via the configuration, which will be dealt with in greater details in the later sections.
HTTP over TCP/IP

HTTP is a clientserver applicationlevel protocol. It typically runs over a TCP/IP connection, as illustrated. HTTP needs not run on TCP/IP. It only presumes a
reliable transport. Any transport protocols that provide such guarantees can be used.
TCP/IP Transmission Control Protocol/Internet Protocol is a set of transport and networklayer protocols for machines to communicate with each other
over the network.
IP Internet Protocol is a networklayer protocol, deals with network addressing and routing. In an IP network, each machine is assigned an unique IP
address e.g., 165.1.2.3, and the IP software is responsible for routing a message from the source IP to the destination IP. In IPv4 IP version 4, the IP
address consists of 4 bytes, each ranges from 0 to 255, separated by dots, which is called a quaddotted form. This numbering scheme supports up to 4G
addresses on the network. The latest IPv6 IP version 6 supports more addresses. Since memorizing number is difficult for most of the people, an english
like domain name, such as www.test101.com is used instead. The DNS Domain Name Service translates the domain name into the IP address via
distributed lookup tables. A special IP address 127.0.0.1 always refers to your own machine. It's domian name is "localhost" and can be used for local
loopback testing.
TCP Transmission Control Protocol is a transportlayer protocol, responsible for establish a connection between two machines. TCP consists of 2 protocols:
TCP and UDP User Datagram Package. TCP is reliable, each packet has a sequence number, and an acknowledgement is expected. A packet will be re
transmitted if it is not received by the receiver. Packet delivery is guaranteed in TCP. UDP does not guarantee packet delivery, and is therefore not reliable.
However, UDP has less network overhead and can be used for applications such as video and audio streaming, where reliability is not critical.
TCP multiplexes applications within an IP machine. For each IP machine, TCP supports multiplexes up to 65536 ports or sockets, from port number 0 to
65535. An application, such as HTTP or FTP, runs or listens at a particular port number for incoming requests. Port 0 to 1023 are preassigned to popular
protocols, e.g., HTTP at 80, FTP at 21, Telnet at 23, SMTP at 25, NNTP at 119, and DNS at 53. Port 1024 and above are available to the users.
Although TCP port 80 is preassigned to HTTP, as the default HTTP port number, this does not prohibit you from running an HTTP server at other user
assigned port number 102465535 such as 8000, 8080, especially for test server. You could also run multiple HTTP servers in the same machine on different
port numbers. When a client issues a URL without explicitly stating the port number, e.g., http://www.test101.com/docs/index.html, the browser will
connect to the default port number 80 of the host www.test101.com. You need to explicitly specify the port number in the URL, e.g.
http://www.test101.com:8000/docs/index.html if the server is listening at port 8000 and not the default port 80.
In brief, to communicate over TCP/IP, you need to know a IP address or hostname, b Port number.
HTTP Specifications
The HTTP specification is maintained by W3C Worldwide Web Consortium and available at http://www.w3.org/standards/techs/http. There are currently
two versions of HTTP, namely, HTTP/1.0 and HTTP/1.1. The original version, HTTP/0.9 1991, written by Tim BernersLee, is a simple protocol for
transferring raw data across the Internet. HTTP/1.0 1996 defined in RFC 1945, improved the protocol by allowing MIMElike messages. HTTP/1.0 does
not address the issues of proxies, caching, persistent connection, virtual hosts, and range download. These features were provided in HTTP/1.1 1999
defined in RFC 2616.
Apache HTTP Server or Apache Tomcat Server

A HTTP server such as Apache HTTP Server or Apache Tomcat Server is needed to study the HTTP protocol.
Apache HTTP server is a popular industrialstrength production server, produced by Apache Software Foundation ASF @ www.apache.org. ASF is an open
source software foundation. That is to say, Apache HTTP server is free, with source code.
The first HTTP server is written by Tim Berners Lee at CERN European Center for Nuclear Research at Geneva, Switzerland, who also invented HTML.
Apache was built on NCSA National Center for Supercomputing Applications, USA "httpd 1.3" server, in early 1995. Apache probably gets its name from
the fact that it consists of some original code from an earlier NCSA httpd web server plus some patches; or from the name of an American Indian tribe.
Read "Apache Howto" on how to install and configuare Apache HTTP server; or "Tomcat Howto" to install and get started with Apache Tomcat Server.
3/21
11/13/2015
HTTP Request and Response Messages

HTTP client and server communicate by sending text messages.The client sends a request message to the server. The server, in turn, returns a response
message.
An HTTP message consists of a message header and an optional message body, separated by a blank line, as illustrated below:
HTTP Request Message

The format of an HTTP request message is as follow:
Request Line
The first line of the header is called the request line, followed by optional request headers.
The request line has the following syntax:
requestmethodnamerequestURIHTTPversion
requestmethodname: HTTP protocol defines a set of request methods, e.g., GET, POST, HEAD, and OPTIONS. The client can use one of these methods
to send a request to the server.
requestURI: specifies the resource requested.
HTTPversion: Two versions are currently in use: HTTP/1.0 and HTTP/1.1.
Examples of request line are:
GET/test.htmlHTTP/1.1
HEAD/query.htmlHTTP/1.0
POST/index.htmlHTTP/1.1
Request Headers
The request headers are in the form of name:value pairs. Multiple values, separated by commas, can be specified.
requestheadername:requestheadervalue1,requestheadervalue2,...
Examples of request headers are:

Host:www.xyz.com
Connection:KeepAlive
AcceptLanguage:usen,fr,cn
Example
The following shows a sample HTTP request message:
4/21
11/13/2015
HTTP Response Message

The format of the HTTP response message is as follows:
Status Line
The first line is called the status line, followed by optional response headers.
The status line has the following syntax:
HTTPversionstatuscodereasonphrase
HTTPversion: The HTTP version used in this session. Either HTTP/1.0 and HTTP/1.1.
statuscode: a 3digit number generated by the server to reflect the outcome of the request.
reasonphrase: gives a short explanation to the status code.
Common status code and reason phrase are "200 OK", "404 Not Found", "403 Forbidden", "500 Internal Server Error".
Examples of status line are:
HTTP/1.1200OK
HTTP/1.0404NotFound
HTTP/1.1403Forbidden
Response Headers
The response headers are in the form name:value pairs:
responseheadername:responseheadervalue1,responseheadervalue2,...
Examples of response headers are:

ContentLength:35
KeepAlive:timeout=15,max=100
The response message body contains the resource data requested.
Example
The following shows a sample response message:
5/21
11/13/2015
HTTP Request Methods

HTTP protocol defines a set of request methods. A client can use one of these request methods to send a request message to an HTTP server. The methods
are:
GET: A client can use the GET request to get a web resource from the server.
HEAD: A client can use the HEAD request to get the header that a GET request would have obtained. Since the header contains the lastmodified date of
the data, this can be used to check against the local cache copy.
POST: Used to post data up to the web server.
PUT: Ask the server to store the data.
DELETE: Ask the server to delete the data.
TRACE: Ask the server to return a diagnostic trace of the actions it takes.
OPTIONS: Ask the server to return the list of request methods it supports.
CONNECT: Used to tell a proxy to make a connection to another host and simply reply the content, without attempting to parse or cache it. This is often
used to make SSL connection through the proxy.
Other extension methods.
"GET" Request Method

GET is the most common HTTP request method.A client can use the GET request method to request or "get" for a piece of resource from an HTTP server.
A GET request message takes the following syntax:
GETrequestURIHTTPversion
(optionalrequestheaders)
(blankline)
(optionalrequestbody)
The keyword GET is case sensitive and must be in uppercase.

requestURI: specifies the path of resource requested, which must begin from the root "/" of the document base directory.
HTTPversion: Either HTTP/1.0 or HTTP/1.1. This client negotiates the protocol to be used for the current session. For example, the client may request to
use HTTP/1.1. If the server does not support HTTP/1.1, it may inform the client in the response to use HTTP/1.0.
The client uses the optional request headers such as Accept, AcceptLanguage, and etc to negotiate with the server and ask the server to deliver the
preferred contents e.g., in the language that the client preferred.
GET request message has an optional request body which contains the query string to be explained later.
Testing HTTP Requests

There are many way to test out the HTTP requests. Your can use utility program such as "telnet" or "hyperterm" search for "telnet.exe" or
"hypertrm.exe" under c:\windows, or write you own network program to send raw request message to an HTTP server to test out the various HTTP
requests.
Telnet
"Telnet" is a very useful networking utility. You can use telnet to establish a TCP connection with a server; and issue raw HTTP requests. For example,
suppose that you have started your HTTP server in the localhost IP address 127.0.0.1 at port 8000:
>telnet
telnet>help
...telnethelpmenu...
telnet>open127.0.0.18000
ConnectingTo127.0.0.1...
GET/index.htmlHTTP/1.0
(Hitentertwicetosendtheterminatingblankline...)
...HTTPresponsemessage...
Telnet is a characterbased protocol.Each character you enter on the telnet client will be sent to the server immediately. Therefore, you cannot make typo
error in entering you raw command, as delete and backspace will be sent to the server.You may have to enable "local echo" option to see the characters
6/21
11/13/2015
you enter. Check the telnet manual search Windows' help for details on using telnet.
Network Program
You could also write your own network program to issue raw HTTP request to an HTTP server. You network program shall first establish a TCP/IP connection
with the server. Once the TCP connection is established, you can issue the raw request.
An example of network program written in Java is as shown assuming that the HTTP server is running on the localhost IP address 127.0.0.1 at port 8000:
importjava.net.*;
importjava.io.*;
publicclassHttpClient{
publicstaticvoidmain(String[]args)throwsIOException{
//Thehostandporttobeconnected.
Stringhost="127.0.0.1";
intport=8000;
//CreateaTCPsocketandconnecttothehost:port.
Socketsocket=newSocket(host,port);
//Createtheinputandoutputstreamsforthenetworksocket.
BufferedReaderin
=newBufferedReader(
newInputStreamReader(socket.getInputStream()));
PrintWriterout
=newPrintWriter(socket.getOutputStream(),true);
//SendrequesttotheHTTPserver.
out.println("GET/index.htmlHTTP/1.0");
out.println();//blanklineseparatingheader&body
out.flush();
//Readtheresponseanddisplayonconsole.
Stringline;
//readLine()returnsnullifserverclosethenetworksocket.
while((line=in.readLine())!=null){
System.out.println(line);
}
//ClosetheI/Ostreams.
in.close();
out.close();
}
}
HTTP/1.0 GET Request

The following shows the response of an HTTP/1.0 GET request issue via telnet or your own network program assuming that you have started your HTTP
server:
(entertwicetocreateablankline)
HTTP/1.1200OK
ETag:"10000000565a52c3e94b66c2e680"
AcceptRanges:bytes
ContentLength:44
Connection:close
Connectiontohostlost.
In this example, the client issues a GET request to ask for a document named "/index.html"; and negotiates to use HTTP/1.0 protocol. A blank line is
needed after the request header. This request message does not contain a body.
The server receives the request message, interprets and maps the requestURI to a document under its document directory. If the requested document is
available, the server returns the document with a response status code "200 OK". The response headers provide the necessary description of the document
returned, such as the lastmodified date LastModified, the MIME type ContentType, and the length of the document ContentLength. The
response body contains the requested document. The browser will format and display the document according to its media type e.g., Plaintext, HTML,
JPEG, GIF, and etc. and other information obtained from the response headers.
Notes:
The request method name "GET" is case sensitive, and must be in uppercase.
If the request method name was incorrectly spelt, the server would return an error message "501 Method Not Implemented".
If the request method name is not allowed, the server will return an error message "405 Method Not Allowed". E.g., DELETE is a valid method name, but
may not be allowed or implemented by the server.
If the requestURI does not exist, the server will return an error message "404 Not Found". You have to issue a proper requestURI, beginning from the
document root "/". Otherwise, the server would return an error message "400 Bad Request".
7/21
11/13/2015
If the HTTPversion is missing or incorrect, the server will return an error message "400 Bad Request".
In HTTP/1.0, by default, the server closes the TCP connection after the response is delivered. If you use telnet to connect to the server, the message
"Connection to host lost" appears immediately after the response body is received. You could use an optional request header "Connection:Keep
Alive" to request for a persistent or keepalive connection, so that another request can be sent through the same TCP connection to achieve better
network efficiency. On the other hand, HTTP/1.1 uses keepalive connection as default.
Response Status Code

The first line of the response message i.e., the status line contains the response status code, which is generated by the server to indicate the outcome of
the request.
The status code is a 3digit number:
1xx Informational: Request received, server is continuing the process.
2xx Success: The request was successfully received, understood, accepted and serviced.
3xx Redirection: Further action must be taken in order to complete the request.
4xx Client Error: The request contains bad syntax or cannot be understood.
5xx Server Error: The server failed to fulfill an apparently valid request.
Some commonly encountered status codes are:
100 Continue: The server received the request and in the process of giving the response.
200 OK: The request is fulfilled.
301 Move Permanently: The resource requested for has been permanently moved to a new location. The URL of the new location is given in the
response header called Location. The client should issue a new request to the new location. Application should update all references to this new
location.
302 Found & Redirect or Move Temporarily: Same as 301, but the new location is temporarily in nature. The client should issue a new request, but
applications need not update the references.
304 Not Modified: In response to the IfModifiedSince conditional GET request, the server notifies that the resource requested has not been
modified.
400 Bad Request: Server could not interpret or understand the request, probably syntax error in the request message.
401 Authentication Required: The requested resource is protected, and require clients credential username/password. The client should resubmit the
request with his credential username/password.
403 Forbidden: Server refuses to supply the resource, regardless of identity of client.
404 Not Found: The requested resource cannot be found in the server.
405 Method Not Allowed: The request method used, e.g., POST, PUT, DELETE, is a valid method. However, the server does not allow that method for the
resource requested.
408 Request Timeout:
414 Request URI too Large:
500 Internal Server Error: Server is confused, often caused by an error in the serverside program responding to the request.
501 Method Not Implemented: The request method used is invalid could be caused by a typing error, e.g., "GET" misspell as "Get".
502 Bad Gateway: Proxy or Gateway indicates that it receives a bad response from the upstream server.
503 Service Unavailable: Server cannot response due to overloading or maintenance. The client can try again later.
504 Gateway Timeout: Proxy or Gateway indicates that it receives a timeout from an upstream server.
More HTTP/1.0 GET Request Examples

Example: Misspelt Request Method
In the request, "GET" is misspelled as "get". The server returns an error "501 Method Not Implemented". The response header "Allow" tells the client the
methods allowed.
get/test.htmlHTTP/1.0
HTTP/1.1501MethodNotImplemented
Allow:GET,HEAD,POST,OPTIONS,TRACE
ContentLength:215
Connection:close
ContentType:text/html;charset=iso88591
<!DOCTYPEHTMLPUBLIC"//IETF//DTDHTML2.0//EN">
<html><head>
<title>501MethodNotImplemented</title>
</head><body>
<h1>MethodNotImplemented</h1>
<p>getto/index.htmlnotsupported.<br/>
</p>
</body></html>
8/21
11/13/2015
Example: 404 File Not Found

In this GET request, the requestURL "/t.html" cannot be found under the servers document directory. The server returns an error "404 Not Found".
GET/t.htmlHTTP/1.0
HTTP/1.1404NotFound
ContentLength:204
Connection:close
<html><head>
<title>404NotFound</title>
</head><body>
<h1>NotFound</h1>
<p>TherequestedURL/t.htmlwasnotfoundonthisserver.</p>
</body></html>
Example: Wrong HTTP Version Number

In this GET request, the HTTPversion was misspelled, resulted in bad syntax. The server returns an error "404 Bad Request". HTTPversion should be either
HTTP/1.0 or HTTP/1.1.
GET/index.htmlHTTTTTP/1.0
HTTP/1.1400BadRequest
Date:Sun,08Feb200401:29:40GMT
Connection:close
<HTML><HEAD>
<TITLE>400BadRequest</TITLE>
</HEAD><BODY>
<H1>BadRequest</H1>
Yourbrowsersentarequestthatthisservercouldnotunderstand.<P>
Therequestlinecontainedinvalidcharactersfollowingtheprotocolstring.<P><P>
</BODY></HTML>
Note: The latest Apache 2.2.14 ignores this error and returns the document with status code "200 OK".
Example: Wrong RequestURI

In the following GET request, the requestURI did not begin from the root "/", resulted in a "bad request".
GETtest.htmlHTTP/1.0
(blankline)
ContentLength:226
Connection:close
<html><head>
<title>400BadRequest</title>
</head><body>
<h1>BadRequest</h1>
<p>Yourbrowsersentarequestthatthisservercouldnotunderstand.<br/>
</p>
</body></html>
Example: KeepAlive Connection

By fault, for HTTP/1.0 GET request, the server closes the TCP connection once the response is delivered. You could request for the TCP connection to be
maintained, so as to send another request using the same TCP connection, to improve on the network efficiency, via an optional request header
"Connection:KeepAlive". The server includes a "Connection:KeepAlive" response header to inform the client that he can send another request
using this connection, before the keepalive timeout. Another response header "KeepAlive:timeout=x,max=x" tells the client the timeout in seconds
and the maximum number of requests that can be sent via this persistent connection.
GET/test.htmlHTTP/1.0
(blankline)
9/21
11/13/2015
HTTP/1.1200OK
ETag:"10000000565a52c3e94b66c2e680"
AcceptRanges:bytes
ContentLength:44
Notes:
The message "Connection to host lost" for telnet appears after "keepalive" timeout
Before the "Connection to host lost" message appears i.e., Keepalive timeout, you can send another request through the same TCP connection.
The header "Connection:Keepalive" is not case sensitive. The space is optional.
If an optional header is misspelled or invalid, it will be ignored by the server.
Example: Accessing a Protected Resource

The following GET request tried to access a protected resource. The server returns an error "403 Forbidden". In this example, the directory
"htdocs\forbidden" is configured to deny all access in the Apache HTTP server configuration file "httpd.conf" as follows:
<Directory"C:/apache/htdocs/forbidden">
Orderdeny,allow
denyfromall
</Directory>
GET/forbidden/index.htmlHTTP/1.0
(blankline)
HTTP/1.1403Forbidden
ContentLength:222
<html><head>
<title>403Forbidden</title>
</head><body>
<h1>Forbidden</h1>
<p>Youdon'thavepermissiontoaccess/forbidden/index.html
onthisserver.</p>
</body></html>
HTTP/1.1 GET Request

HTTP/1.1 server supports socalled virtual hosts. That is, the same physical server could house several virtual hosts, with different hostnames e.g.,
www.test101.com and www.test909.com and their own dedicated document root directories. Hence, in an HTTP/1.1 GET request, it is mandatory to
include a request header called "Host", to select one of the virtual hosts.
Example: HTTP/1.1 Request

HTTP/1.1 maintains persistent or keepalive connection by default to improve the network efficiency. You can use a request header "Connection:Close"
to ask the server to close the TCP connection once the response is delivered.
Host:127.0.0.1
(blankline)
HTTP/1.1200OK
ETag:"10000000565a52c3e94b66c2e680"
AcceptRanges:bytes
ContentLength:44
Example: HTTP/1.1 Missing Host Header

The following example shows that "Host" header is mandatory in an HTTP/1.1 request. If "Host" header is missing, the server returns an error "400 Bad
10/21
11/13/2015
Request".
(blankline)
ContentLength:226
Connection:close
<html><head>
<title>400BadRequest</title>
</head><body>
<h1>BadRequest</h1>
<p>Yourbrowsersentarequestthatthisservercouldnotunderstand.<br/>
</p>
</body></html>
Conditional GET Requests

In all the previous examples, the server returns the entire document if the request can be fulfilled i.e. unconditional. You may use additional request header
to issue a "conditional request". For example, to ask for the document based on the lastmodified date so as to decide whether to use the local cache copy,
or to ask for a portion of the document or range instead of the entire document useful for downloading large documents.
The conditional request headers include:
IfModifiedSince check for response status code "304 Not Modified".
IfUnmodifiedSince
IfMatch
IfNoneMatch
IfRange
Request Headers
This section describes some of the commonlyused request headers. Refer to HTTP Specification for more details. The syntax of header name is words with
initialcap joined using dash , e.g., ContentLength, IfModifiedSince.
Host:domainname HTTP/1.1 supports virtual hosts. Multiple DNS names e.g., www.test101.com and www.test102.com can reside on the same physical
server, with their own document root directories. Host header is mandatory in HTTP/1.1 to select one of the hosts.
The following headers can be used for content negotiation by the client to ask the server to deliver the preferred type of the document in terms of the
media type, e.g. JPEG vs. GIF, or language used e.g. English vs. French if the server maintain multiple versions for the same document.
Accept:mimetype1,mimetype2,... The client can use the Accept header to tell the server the MIME types it can handle and it prefers. If the
server has multiple versions of the document requested e.g., an image in GIF and PNG, or a document in TXT and PDF, it can check this header to decide
which version to deliver to the client. E.g., PNG is more advanced more GIF, but not all browser supports PNG. This process is called contenttype
negotiation.
AcceptLanguage:language1,language2,... The client can use the AcceptLanguage header to tell the server what languages it can handle or
it prefers. If the server has multiple versions of the requested document e.g., in English, Chinese, French, it can check this header to decide which version to
return. This process is called language negotiation.
AcceptCharset:Charset1,Charset2,... For character set negotiation, the client can use this header to tell the server which character sets it can
handle or it prefers. Examples of character sets are ISO88591, ISO88592, ISO88595, BIG5, UCS2, UCS4, UTF8.
AcceptEncoding:encodingmethod1,encodingmethod2,... The client can use this header to tell the server the type of encoding it supports. If
the server has encoded or compressed version of the document requested, it can return an encoded version supported by the client. The server can also
choose to encode the document before returning to the client to reduce the transmission time. The server must set the response header "Content
Encoding" to inform the client that the returned document is encoded. The common encoding methods are "xgzip .gz, .tgz" and "xcompress .Z".
Connection:Close|KeepAlive The client can use this header to tell the server whether to close the connection after this request, or to keep the
connection alive for another request. HTTP/1.1 uses persistent keepalive connection by default. HTTP/1.0 closes the connection by default.
Referer:refererURL The client can use this header to indicate the referrer of this request. If you click a link from web page 1 to visit web page 2, web
page 1 is the referrer for request to web page 2. All major browsers set this header, which can be used to track where the request comes from for web
advertising, or content customization. Nonetheless, this header is not reliable and can be easily spoofed. Note that Referrer is misspelled as "Referer"
unfortunately, you have to follow too.
UserAgent: browsertype Identify the type of browser used to make the request. Server can use this information to return different document
depending on the type of browsers.
ContentLength:numberofbytes Used by POST request, to inform the server the length of the request body.
ContentType:mimetype Used by POST request, to inform the server the media type of the request body.
CacheControl:nocache|... The client can use this header to specify how the pages are to be cached by proxy server. "nocache" requires proxy to
11/21
11/13/2015
obtain a fresh copy from the original server, even though a local cached copy is available. HTTP/1.0 server does not recognize "CacheControl: no
cache". Instead, it uses "Pragma:nocache". Included both request headers if you are not sure about the servers version.
Authorization: Used by the client to supply its credential username/password to access protected resources. This header will be described in later
chapter on authentication.
Cookie:cookiename1=cookievalue1,cookiename2=cookievalue2,... The client uses this header to return the cookies back to the
server, which was set by this server earlier for state management. This header will be discussed in later chapter on state management.
IfModifiedSince:date Tell the server to send the page only if it has been modified after the specific date.
GET Request for Directory

Suppose that a directory called "testdir" is present in the document base directory "htdocs".
If a client issues a GET request to "/testdir/" i.e., at the directory.
1. The server will return "/testdir/index.html" if the directory contains a "index.html" file.
2. Otherwise, the server returns the directory listing, if directory listing is enabled in the server configuration.
3. Otherwise, the server returns "404 Page Not Found".
It is interesting to take note that if a client issue a GET request to "/testdir" without specifying the directory path "/", the server returns a "301 Move
Permanently" with a new "Location" of "/testdir/", as follows.
GET/testdirHTTP/1.1
Host:127.0.0.1
(blankline)
HTTP/1.1301MovedPermanently
Location:http://127.0.0.1:8000/testdir/
ContentLength:238
<html><head>
<title>301MovedPermanently</title>
</head><body>
<h1>MovedPermanently</h1>
<p>Thedocumenthasmoved<ahref="http://127.0.0.1:8000/testdir/">here</a>.</p>
</body></html>
Most of the browser will follow up with another request to "/testdir/". For example, If you issue http://127.0.0.1:8000/testdir without the trailing
"/" from a browser, you could notice that a trailing "/" was added to the address after the response was given. The morale of the story is: you should include
the "/" for directory request to save you an additional GET request.
Issue a GET Request through a Proxy Server

To send a GET request through a proxy server, a establish a TCP connection to the proxy server; b use an absolute requestURI
http://hostname:port/path/fileName to the target server.
The following trace was captured using telnet. A connection is established with the proxy server, and a GET request issued. Absolute requestURI is used in
the request line.
GEThttp://www.amazon.com/index.htmlHTTP/1.1
Host:www.amazon.com
Connection:Close
(blankline)
HTTP/1.1302Found
TransferEncoding:chunked
Date:Fri,27Feb200409:27:35GMT
Connection:close
Server:Stronghold/2.4.2Apache/1.3.6C2NetEU/2412(Unix)
SetCookie:skin=;domain=.amazon.com;path=/;expires=Wed,01Aug0112:00:00GMT
Connection:close
Location:http://www.amazon.com:80/exec/obidos/subst/home/home.html
Via:1.1xproxy(NetCacheNetApp/5.3.1R4D5)
ed
<HTML><HEAD>
<TITLE>302Found</TITLE>
</HEAD><BODY>
<H1>Found</H1>
Thedocumenthasmoved
<AHREF="http://www.amazon.com:80/exec/obidos/subst/home/home.html">
here</A>.<P>
</BODY></HTML>
12/21
11/13/2015
Take note that the response is returned in "chunks".
"HEAD" Request Method

HEAD request is similar to GET request. However, the server returns only the response header without the response body, which contains the actual
document. HEAD request is useful for checking the headers, such as LastModified, ContentType, ContentLength, before sending a proper GET
request to retrieve the document.
The syntax of the HEAD request is as follows:
HEADrequestURIHTTPversion
(otheroptionalrequestheaders)
(blankline)
Example
HEAD/index.htmlHTTP/1.0
(blankline)
HTTP/1.1200OK
ETag:"10000000565a52c3e94b66c2e680"
AcceptRanges:bytes
ContentLength:44
Connection:close
Notice that the response consists of the header only without the body, which contains the actual document.
"OPTIONS" Request Method

A client can use an OPTIONS request method to query the server which request methods are supported. The syntax for OPTIONS request message is:
OPTIONSrequestURI|*HTTPversion
(otheroptionalheaders)
(blankline)
"*" can be used in place of a requestURI to indicate that the request does not apply to any particular resource.
Example
For example, the following OPTIONS request is sent through a proxy server:
OPTIONShttp://www.amazon.com/HTTP/1.1
Host:www.amazon.com
Connection:Close
(blankline)
HTTP/1.1200OK
ContentLength:0
Connection:close
Allow:GET,HEAD,POST,OPTIONS,TRACE
Connection:close
(blankline)
All servers that allow GET request will allow HEAD request. Sometimes, HEAD is not listed.
"TRACE" Request Method

A client can send a TRACE request to ask the server to return a diagnostic trace.
TRACE request takes the following syntax:
TRACE/HTTPversion
(blankline)
Example
The following example shows a TRACE request issued through a proxy server.
13/21
11/13/2015
TRACEhttp://www.amazon.com/HTTP/1.1
Host:www.amazon.com
Connection:Close
(blankline)
HTTP/1.1200OK
ContentType:message/http
Connection:close
Connection:close
9d
TRACE/HTTP/1.1
Connection:keepalive
Host:www.amazon.com
XForwardedFor:155.69.185.59,155.69.5.234
To compare the TRACE request with trace route
Submitting HTML Form Data and Query String

In many Internet applications, such as ecommerce and search engine, the clients are required to submit additional information to the server e.g., the name,
address, the search keywords. Based on the data submitted, the server takes an appropriate action and produces a customized response.
The clients are usually presented with a form produced using HTML <form> tag. Once they fill in the requested data and hit the submit button, the
browser packs the form data and submits them to the server, using either a GET request or a POST request.
The following is a sample HTML form, which is produced by the following HTML script:
<html>
<head><title>ASampleHTMLForm</title></head>
<body>
<h2align="left">ASampleHTMLDataEntryForm</h2>
<formmethod="get"action="/bin/process">
Enteryourname:<inputtype="text"name="username"><br/>
Enteryourpassword:<inputtype="password"name="password"><br/>
Whichyear?
<inputtype="radio"name="year"value="2"/>Yr1
<inputtype="radio"name="year"value="2"/>Yr2
<inputtype="radio"name="year"value="3"/>Yr3<br/>
Subjectregistered:
<inputtype="checkbox"name="subject"value="e101"/>E101
<inputtype="checkbox"name="subject"value="e102"/>E102
<inputtype="checkbox"name="subject"value="e103"/>E103<br/>
SelectDay:
<selectname="day">
<optionvalue="mon">Monday</option>
<optionvalue="wed">Wednesday</option>
<optionvalue="fri">Friday</option>
</select><br/>
<textarearows="3"cols="30">Enteryourspecialrequesthere</textarea><br/>
<inputtype="submit"value="SEND"/>
<inputtype="reset"value="CLEAR"/>
<inputtype="hidden"name="action"value="registration"/>
</form>
</body>
</html>
A form contains fields. The types of field include:
14/21
11/13/2015
Text Box: produced by <inputtype="text">.

Password Box: produced by <inputtype="password">.
Radio Button: produced by <inputtype="radio">.
Checkbox: produced by <inputtype="checkbox">.
Selection: produced by <select> and <option>.
Text Area: produced by <textarea>.
Submit Button: produced by <inputtype="submit">.
Reset Button: produced by <inputtype="reset">.
Hidden Field: produced by <inputtype="hidden">.
Button: produced by <inputtype="button">.
Each field has a name and can take on a specified value. Once the client fills in the fields and hits the submit button, the browser gathers each of the fields'
name and value, packed them into "name=value" pairs, and concatenates all the fields together using "&" as the field separator. This is known as a query
string. It will send the query string to the server as part of the request.
name1=value1&name2=value2&name3=value3&...
Special characters are not allowed inside the query string. They must be replaced by a "%" followed by the ASCII code in Hex. E.g., "~" is replaced by "%7E",
"#" by "%23" and so on. Since blank is rather common, it can be replaced by either "%20" or "+" the "+" character must be replaced by "%2B". This
replacement process is called URLencoding, and the result is a URLencoded query string. For example, suppose that there are 3 fields inside a form, with
name/value of "name=Peter Lee", "address=#123 Happy Ave" and "language=C++", the URLencoded query string is:
name=Peter+Lee&address=%23123+Happy+Ave&Language=C%2B%2B
The query string can be sent to the server using either HTTP GET or POST request method, which is specified in the <form>'s attribute "method".
<formmethod="get|post"action="url">
If GET request method is used, the URLencoded query string will be appended behind the requestURI after a "?" character, i.e.,
GETrequestURI?querystringHTTPversion
(blankline)
Using GET request to send the query string has the following drawbacks:
The amount of data you could append behind requestURI is limited. If this amount exceed a serverspecific threshold, the server would return an error
"414 Request URI too Large".
The URLencoded query string would appear on the address box of the browser.
POST method overcomes these drawbacks. If POST request method is used, the query string will be sent in the body of the request message, where the
amount is not limited. The request headers ContentType and ContentLength are used to notify the server the type and the length of the query string.
The query string will not appear on the browsers address box. POST method will be discussed later.
Example
The following HTML form is used to gather the username and password in a login menu.
<html>
<head><title>Login</title></head>
<body>
<h2>LOGIN</h2>
<formmethod="get"action="/bin/login">
Username:<inputtype="text"name="user"size="25"/><br/>
Password:<inputtype="password"name="pw"size="10"/><br/><br/>
<inputtype="hidden"name="action"value="login"/>
</form>
</body>
</html>
The HTTP GET request method is used to send the query string. Suppose the user enters "Peter Lee" as the username, "123456" as password; and clicks the
submit button. The following GET request is:
GET/bin/login?user=Peter+Lee&pw=123456&action=loginHTTP/1.1
Referer:http://127.0.0.1:8000/login.html
AcceptLanguage:enus
15/21
11/13/2015
Host:127.0.0.1:8000
Note that although the password that you enter does not show on the screen, it is shown clearly in the address box of the browser. You should never use
send your password without proper encryption.
http://127.0.0.1:8000/bin/login?user=Peter+Lee&pw=123456&action=login
URL and URI

URL Uniform Resource Locator
A URL Uniform Resource Locator, defined in RFC 2396, is used to uniquely identify a resource over the web. URL has the following syntax:
protocol://hostname:port/pathandfilename
There are 4 parts in a URL:

1. Protocol: The applicationlayer protocol used by the client and server, e.g., HTTP, FTP, and telnet.
2. Hostname: The DNS domain name e.g., www.test101.com or IP address e.g., 192.128.1.2 of the server.
3. Port: The TCP port number that the server is listening for incoming requests from the clients.
4. Pathandfilename: The name and location of the requested resource, under the server document base directory.
For example, in the URL http://www.test101.com/docs/index.html, the communication protocol is HTTP; the hostname is www.test101.com. The port
number was not specified in the URL, and takes on the default number, which is TCP port 80 for HTTP [STD 2]. The path and file name for the resource to be
located is "/docs/index.html".
Other examples of URL are:
ftp://www.ftp.org/docs/test.txt
mailto:user@test101.com
news:soc.culture.Singapore
telnet://www.test101.com/
Encoded URL
URL cannot contain special characters, such as blank or '~'. Special characters are encoded, in the form of %xx, where xx is the ASCII hex code. For example,
'~' is encoded as %7e; '+' is encoded as %2b. A blank can be encoded as %20 or '+'. The URL after encoding is called encoded URL.
URI Uniform Resource Identifier

URI Uniform Resource Identifier, defined in RFC3986, is more general than URL, which can even locate a fragment within a resource. The URI syntax for
HTTP protocol is:
http://host:port/path?requestparameters#nameAnchor
The request parameters, in the form of name=value pairs, are separated from the URL by a '?'. The name=value pairs are separated by a '&'.
The #nameAnchor identifies a fragment within the HTML document, defined via the anchor tag <aname="anchorName">...</a>.
URL rewriting for session management, e.g., "...;sessionID=xxxxxx".
"POST" Request Method

POST request method is used to "post" additional data up to the server e.g., submitting HTML form data or uploading a file. Issuing an HTTP URL from the
browser always triggers a GET request. To trigger a POST request, you can use an HTML form with attribute method="post" or write your own network
program. For submitting HTML form data, POST request is the same as the GET request except that the URLencoded query string is sent in the request
body, rather than appended behind the requestURI.
The POST request takes the following syntax:
POSTrequestURIHTTPversion
ContentType:mimetype
ContentLength:numberofbytes
(URLencodedquerystring)
Request headers ContentType and ContentLength is necessary in the POST request to inform the server the media type and the length of the request
body.
Example: Submitting Form Data using POST Request Method

We use the same HTML script as above, but change the request method to POST.
<html>
<head><title>Login</title></head>
<body>
16/21
11/13/2015
<h2>LOGIN</h2>
<formmethod="post"action="/bin/login">
Username:<inputtype="text"name="user"size="25"/><br/>
Password:<inputtype="password"name="pw"size="10"/><br/><br/>
<inputtype="hidden"name="action"value="login"/>
</form>
</body>
</html>
Suppose the user enters "Peter Lee" as username and "123456" as password, and clicks the submit button, the following POST request would be generated
by the browser:
POST/bin/loginHTTP/1.1
Host:127.0.0.1:8000
Referer:http://127.0.0.1:8000/login.html
AcceptLanguage:enus
ContentType:application/xwwwformurlencoded
ContentLength:37
CacheControl:nocache
User=Peter+Lee&pw=123456&action=login
Note that the ContentType header informs the server the data is URLencoded with a special MIME type application/xwwwformurlencoded, and
the ContentLength header tells the server how many bytes to read from the message body.
POST vs GET for Submitting Form Data

As mentioned in the previous section, POST request has the following advantage compared with the GET request in sending the query string:
The amount of data that can be posted is unlimited, as they are kept in the request body, which is often sent to the server in a separate data stream.
The query string is not shown on the address box of the browser.
Note that although the password is not shown on the browsers address box, it is transmitted to the server in clear text, and subjected to network sniffing.
Hence, sending password using a POST request is absolutely not secure.
File Upload using multipart/formdata POST Request

"RFC 1867: Formbased File upload in HTML" specifies how a file can be uploaded to the server using a POST request from an HTML form. A new attribute
type="file" was added to the <input> tag of HTML <form> to support file upload. The fileupload POST data is not URLencoded in the standard
application/xwwwformurlencoded, but uses a new MIME type of multipart/formdata.
Example
The following HTML form can be used for file upload:
<html>
<head><title>FileUpload</title></head>
<body>
<h2>UploadFile</h2>
<formmethod="post"enctype="multipart/formdata"action="servlet/UploadServlet">
Whoareyou:<inputtype="text"name="username"/><br/>
Choosethefiletoupload:
<inputtype="file"name="fileID"/><br/>
</form>
</body>
</html>
When the browser encountered an <input> tag with attribute type="file", it displays a text box and a "browse..." button, to allow user to choose the file
to be uploaded.
When the user clicks the submit button, the browser send the form data and the content of the selected files. The old encoding type "application/x
wwwformurlencoded" is inefficient for sending binary data and nonASCII characters. A new media type "multipart/formdata" is used instead.
Each part identifies the input name within the original HTML form, and the content type if the media is known, or as application/octetstream
otherwise.
The original local file name could be supplied as a "filename" parameter, or in the "ContentDisposition:formdata" header.
17/21
11/13/2015
An example of the POST message for file upload is as follows:

POST/bin/uploadHTTP/1.1
Host:test101
AcceptLanguage:enus
ContentType:multipart/formdata;boundary=7d41b838504d8
ContentLength:342
7d41b838504d8ContentDisposition:formdata;name="username"
PeterLee
7d41b838504d8ContentDisposition:formdata;name="fileID";filename="C:\temp.html"ContentType:text/plain
<h1>Homepageonmainserver</h1>
7d41b838504d8
Servlet 3.0 provides builtin support for processing file upload. Read "Uploading Files in Servlet 3.0".
"CONNECT" Request Method

The HTTP CONNECT request is used to ask a proxy to make a connection to anther host and simply relay the content, rather than attempting to parse or
cache the message. This is often used to make a connection through a proxy.
Under Construction
Other Request Methods

PUT: Ask the server to store the data.
DELETE: Ask the server to delete the data.
For security consideration, PUT and DELETE are not supported by most of the production server.
Extension methods also error codes and headers can be defined to extend the functionality of the HTTP protocol.
Under Construction
Content Negotiation
As mention earlier, HTTP support content negotiation between the client and the server. A client can use additional request headers such as Accept,
AcceptLanguage, AcceptCharset, AcceptEncoding to tell the server what it can handle or which content it prefers. If the server possesses multiple
versions of the same document in different format, it will return the format that the client prefers. This process is called content negotiation.
ContentType Negotiation
The server uses a MIME configuration file called "conf\mime.types" to map the file extension to a media type, so that it can ascertain the media type of
the file by looking at its file extension. For example, file extensions ".htm", ".html" are associated with MIME media type "text/html", file extension of
".jpg", ".jpeg" are associated with "image/jpeg". When a file is returned to the client, the server has to put up a ContentType response header to inform
the client the media type of the data.
For contenttype negotiation, suppose that the client requests for a file call "logo" without specifying its type, and sends an header "Accept:image/gif,
image/jpeg,...". If the server has 2 formats of the "logo": "logo.gif" and "logo.jpg", and the MIME configuration file have the following entries:
image/gifgif
image/jpegjpegjpgjpe
The server will return "logo.gif" to the client, based on the client Accept header, and the MIME type/file mapping. The server will include a "Content
type:image/gif" header in its response.
The message trace is shown:
GET/logoHTTP/1.1
Accept:image/gif,image/xxbitmap,image/jpeg,image/pjpeg,
application/xshockwaveflash,application/vnd.msexcel,
application/vnd.mspowerpoint,application/msword,*/*
AcceptLanguage:enus
Host:test101:8080
(blankline)
HTTP/1.1200OK
ContentLocation:logo.gif
Vary:negotiate,accept
TCN:choice
18/21
11/13/2015
LastModified:Wed,21Feb199619:45:52GMT
ETag:"0916312b7670;404142de"
AcceptRanges:bytes
ContentLength:2326
ContentType:image/gif
(blankline)
(bodyomitted)
However, if the server has 3 "logo.*" files, "logo.gif", "logo.html", "logo.jpg", and "Accept:*/*" was used:
GET/logoHTTP/1.1
Accept:*/*
AcceptLanguage:enus
Host:test101:8080
(blankline)
HTTP/1.1200OK
ContentLocation:logo.html
Vary:negotiate,accept
TCN:choice
LastModified:Fri,20Feb200404:31:17GMT
ETag:"01040358d95;404144c1"
AcceptRanges:bytes
ContentLength:16
(blankline)
(bodyomitted)
Accept:*/*
The following Apaches configuration directives are relevant to contenttype negotiation:

The TypeConfig directive can be used to specify the location of the MIME mapping file:
TypeConfigconf/mime.types
The AddType directive can be used to include additional MIME type mapping in the configuration file:
AddTypemimetypeextension1[extension2]
The DefaultType directive gives the MIME type of an unknown file extension in the ContentType response header
DefaultTypetext/plain
Language Negotiation and "Options MultiView"

The "OptionsMultiView" directive is the simpler way to implement language negotiation. For Example:
AddLanguageen.en
<Directory"C:/_javabin/Apache1.3.29/htdocs">
OptionsIndexesMultiViews
</Directory>
Suppose that the client requests for "index.html" and send an "AcceptLanguage: enus". If the server has "test.html", "test.html.en" and
"test.html.cn", based on the clients preference, "test.html.en" will be returned. "en" includes "enus".
A message trace is as follows:
Accept:*/*
AcceptLanguage:enus
Host:test101:8080
(blankline)
HTTP/1.1200OK
ContentLocation:index.html.en
Vary:negotiate
TCN:choice
LastModified:Sun,29Feb200402:07:45GMT
ETag:"01340414971;40414964"
AcceptRanges:bytes
ContentLength:19
19/21
11/13/2015
ContentLanguage:en
(blankline)
(bodyomitted)
The AddLanguage directive is needed to associate a language code with a file extension, similar to MIME type/file mapping.
Note that "OptionsAll" directive does not include "MultiViews" option. That is, you have to explicitly turn on MultiViews.
The directive LanguagePriority can be used to specify the language preference in case of a tie during content negotiation or if the client does not express
a preference. For example:
<IfModulemod_negotiation.c>
LanguagePriorityendanletfrdeelitjakrnoplptptbr
</IfModule>
Character Set Negotiation

A client can use the request header AcceptCharset to negotiate with the server for the character set it prefers.
AcceptCharset:charset1,charset2,...
The commonly encountered character sets include: ISO88591 LatinI, ISO88592, ISO88595, BIG5 Chinese Traditional, GB2312 Chinese Simplified,
UCS2 2byte Unicode, UCS4 4byte Unicode, UTF8 Encoded Unicode, and etc.
Similarly, the AddCharset directive is used to associate the file extension with the character set. For example:
AddCharsetISO88598.iso88598
AddCharsetISO2022JP.jis
AddCharsetBig5.Big5.big5
AddCharsetWINDOWS1251.cp1251
AddCharsetCP866.cp866
AddCharsetISO88595.isoru
AddCharsetKOI8R.koi8r
AddCharsetUCS2.ucs2
AddCharsetUCS4.ucs4
AddCharsetUTF8.utf8
Encoding Negotiation
A client can use the AcceptEncoding header to tell the server the type of encoding it supports. The common encoding schemes are: "xgzip (.gz,
.tgz)" and "xcompress(.Z)".
AcceptEncoding:encodingmethod1,encodingmethod2,...
Similarly, the AddEncoding directive is used to associate the file extension with the an encoding scheme. For example:
AddEncodingxcompress.Z
AddEncodingxgzip.gz.tgz
Persistent (or Keepalive) Connections

In HTTP/1.0, the server closes the TCP connection after delivering the response by default Connection:Close. That is, each TCP connection services only
one request. This is not efficiency as many HTML pages contain hyperlinks via <ahref="url"> tag to other resources such as images, scripts either
locally or from a remote server. If you download a page containing 5 inline images, the browser has to establish TCP connection 6 times to the same server.
The client can negotiate with the server and ask the server not to close the connection after delivering the response, so that another request can be sent
through the same connection. This is known as persistent connection or keepalive connection. Persistent connections greatly enhance the efficiency of the
network. For HTTP/1.0, the default connection is nonpersistent. To ask for persistent connection, the client must include a request header "Connection:
Keepalive" in the request message to negotiate with the server.
For HTTP/1.1, the default connection is persistent. The client do not have to sent the "Connection:Keepalive" header. Instead, the client may wish to
send the header "Connection:Close" to ask the server to close the connection after delivering the response.
Persistent connection is extremely useful for web pages with many small inline images and other associated data, as all these can be downloaded using the
same connection. The benefits for persistent connection are:
CPU time and resource saving in opening and closing TCP connection in client, proxy, gateways, and the origin server.
Request can be "pipelined". That is, a client can make several requests without waiting for each response, so as to use the network more efficiently.
Faster response as no time needed to perform TCPs connection opening handshaking.
In Apache HTTP server, several configuration directives are related to the persistent connections:
The KeepAlive directive decides whether to support persistent connections. This takes value of either On or Off.
KeepAliveOn|Off
The MaxKeepAliveRequests directive sets the maximum number of requests that can be sent through a persistent connection. You can set to 0 to allow
unlimited number of requests. It is recommended to set to a high number for better performance and network efficiency.
20/21
11/13/2015
MaxKeepAliveRequests200
The KeepAliveTimeOut directive set the time out in seconds for a persistent connection to wait for the next request.
KeepAliveTimeout10
Range Download
AcceptRanges:bytes
Under Construction
Cache Control
The client can send a request header "Cachecontrol:nocache" to tell the proxy to get a fresh copy from the original server, even thought there is a
local cached copy. Unfortunately, HTTP/1.0 server does not understand this header, but uses an older request header "Pragma: nocache". You could
include both headers in your request.
Pragma:nocache
More, Under Construction
REFERENCES & RESOURCES

W3C HTTP specifications at http://www.w3.org/standards/techs/http.
RFC 2616 "Hypertext Transfer Protocol HTTP/1.1", 1999 @ http://www.ietf.org/rfc/rfc2616.txt.
RFC 1945 "Hypertext Transfer Protocol HTTP/1.0", 1996 @ http://www.ietf.org/rfc/rfc1945.txt.
STD 2: "Assigned numbers", 1994.
STD 5: "Internet Protocol IP", 1981.
STD 6:"User Datagram Protocol UDP", 1980.
STD 7:"Transmission Control Protocol TCP", 1983.
RFC 2396: "Uniform Resource Identifiers URI: Generic Syntax", 1998.
RFC 2045: "Multipurpose Internet Mail Extension MIME Part 1: Format of Internet Message Bodies", 1996.
RFC 1867: "Formbased File upload in HTML", 1995, obsoleted by RFC2854.
RFC 2854: "The text/html media type", 2000.
Mutlipart Servlet for file upload @ www.servlets.com
Latest version tested: HTTP 1.1, Apache HTTP Server 2.2.14

Last modified: October 20, 2009
Feedback, comments, corrections, and errata can be sent to Chua HockChuan ehchua@ntu.edu.sg | HOME
21/21

In Introduction To HTTP Basics

Uploaded by

Copyright:

Available Formats

In Introduction To HTTP Basics

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

In Introduction To HTTP Basics

Uploaded by

Copyright:

Available Formats

11/13/2015

HTTP (HyperText Transfer Protocol)

HyperText Transfer Protocol HTTP

Uniform Resource Locator URL

There are 4 parts in a URL:

HTTP over TCP/IP

Apache HTTP Server or Apache Tomcat Server

HTTP Request and Response Messages

HTTP Request Message

Examples of request headers are:

HTTP Response Message

Examples of response headers are:

The response message body contains the resource data requested.

HTTP Request Methods

"GET" Request Method

The keyword GET is case sensitive and must be in uppercase.

Testing HTTP Requests

HTTP/1.0 GET Request

Response Status Code

More HTTP/1.0 GET Request Examples

Example: 404 File Not Found

Example: Wrong HTTP Version Number

Example: Wrong RequestURI

Example: KeepAlive Connection

Example: Accessing a Protected Resource

HTTP/1.1 GET Request

Example: HTTP/1.1 Request

Example: HTTP/1.1 Missing Host Header

Conditional GET Requests

GET Request for Directory

Issue a GET Request through a Proxy Server

Take note that the response is returned in "chunks".

"HEAD" Request Method

"OPTIONS" Request Method

"TRACE" Request Method

To compare the TRACE request with trace route

Submitting HTML Form Data and Query String

A form contains fields. The types of field include:

Text Box: produced by <inputtype="text">.

URL and URI

There are 4 parts in a URL:

URI Uniform Resource Identifier

"POST" Request Method

Example: Submitting Form Data using POST Request Method

POST vs GET for Submitting Form Data

File Upload using multipart/formdata POST Request

An example of the POST message for file upload is as follows:

"CONNECT" Request Method

Other Request Methods

The following Apaches configuration directives are relevant to contenttype negotiation:

Language Negotiation and "Options MultiView"

Character Set Negotiation

Persistent (or Keepalive) Connections

More, Under Construction

REFERENCES & RESOURCES

Latest version tested: HTTP 1.1, Apache HTTP Server 2.2.14

You might also like