Home > Articles > Programming > Java

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

17.8 Example: A Simple HTTP Server

In Listing 17.19 we adapt the NetworkServer class to act as an HTTP server. Rather than returning files, however, we have the server simply echo back the received input by storing all of the input lines, then transmit back an HTML file that shows the sent line. Although writing programs that output HTML seems odd, in Chapter 19 (Server-Side Java: Servlets) and Chapter 24 (JavaScript: Adding Dynamic Content to Web Pages) you'll see that this is actually common practice. Furthermore, having a program that can act as an HTTP server but returns a Web page showing the received input is a useful debugging tool when you are working with HTTP clients and servlet or JSP programming. You'll see this class used many times in the HTTP and servlet chapters.

Listing 17.19 EchoServer.java

import java.net.*;
import java.io.*;
import java.util.StringTokenizer;

/** A simple HTTP server that generates a Web page showing all
 * of the data that it received from the Web client (usually
 * a browser). To use this server, start it on the system of
 * your choice, supplying a port number if you want something
 * other than port 8088. Call this system server.com. Next,
 * start a Web browser on the same or a different system, and
 * connect to http://server.com:8088/whatever. The resultant
 * Web page will show the data that your browser sent. For 
 * debugging in servlet or CGI programming, specify 
 * http://server.com:8088/whatever as the ACTION of your HTML
 * form. You can send GET or POST data; either way, the
 * resultant page will show what your browser sent.
 */

public class EchoServer extends NetworkServer {
 protected int maxRequestLines = 50;
 protected String serverName = "EchoServer";

 /** Supply a port number as a command-line
  * argument. Otherwise, use port 8088.
  */
 
 public static void main(String[] args) {
  int port = 8088;
  if (args.length > 0) {
   try {
    port = Integer.parseInt(args[0]);
   } catch(NumberFormatException nfe) {}
  }
  new EchoServer(port, 0);
 }

 public EchoServer(int port, int maxConnections) {
  super(port, maxConnections);
  listen();
 }
 /** Overrides the NetworkServer handleConnection method to 
  * read each line of data received, save it into an array
  * of strings, then send it back embedded inside a PRE 
  * element in an HTML page.
  */
 
 public void handleConnection(Socket server)
   throws IOException{
  System.out.println
    (serverName + ": got connection from " +
     server.getInetAddress().getHostName());
  BufferedReader in = SocketUtil.getReader(server);
  PrintWriter out = SocketUtil.getWriter(server);
  String[] inputLines = new String[maxRequestLines];
  int i;
  for (i=0; i<maxRequestLines; i++) {
   inputLines[i] = in.readLine();
   if (inputLines[i] == null) // Client closed connection.
    break;
   if (inputLines[i].length() == 0) { // Blank line.
    if (usingPost(inputLines)) {
     readPostData(inputLines, i, in);
     i = i + 2;
    }
    break;
   }
  }
  printHeader(out);
  for (int j=0; j<i; j++) {
   out.println(inputLines[j]);
  }
  printTrailer(out);
  server.close();
 }

 // Send standard HTTP response and top of a standard Web page.
 // Use HTTP 1.0 for compatibility with all clients.
 
 private void printHeader(PrintWriter out) {
  out.println
   ("HTTP/1.0 200 OK\r\n" +
    "Server: " + serverName + "\r\n" +
    "Content-Type: text/html\r\n" +
    "\r\n" +
    "<HTML>\n" +
    "<!DOCTYPE HTML PUBLIC " +
     "\"-//W3C//DTD HTML 4.0 Transitional//EN\">\n" +
    "<HEAD>\n" +
    " <TITLE>" + serverName + " Results</TITLE>\n" +
    "</HEAD>\n" +
    "\n" +
    "<BODY BGCOLOR=\"#FDF5E6\">\n" +
    "<H1 ALIGN=\"CENTER\">" + serverName +
     " Results</H1>\n" +
    "Here is the request line and request headers\n" +
    "sent by your browser:\n" +
    "<PRE>");
 }

 // Print bottom of a standard Web page.
 
 private void printTrailer(PrintWriter out) {
  out.println
   ("</PRE>\n" +
    "</BODY>\n" +
    "</HTML>\n");
 }

 // Normal Web page requests use GET, so this server can simply
 // read a line at a time. However, HTML forms can also use 
 // POST, in which case we have to determine the number of POST
 // bytes that are sent so we know how much extra data to read
 // after the standard HTTP headers.
 
 private boolean usingPost(String[] inputs) {
  return(inputs[0].toUpperCase().startsWith("POST"));
 }

 private void readPostData(String[] inputs, int i,
              BufferedReader in)
   throws IOException {
  int contentLength = contentLength(inputs);
  char[] postData = new char[contentLength];
  in.read(postData, 0, contentLength);
  inputs[++i] = new String(postData, 0, contentLength);
 }
(continued)
 // Given a line that starts with Content-Length,
 // this returns the integer value specified.
 
 private int contentLength(String[] inputs) {
  String input;
  for (int i=0; i<inputs.length; i++) {
   if (inputs[i].length() == 0)
    break;
   input = inputs[i].toUpperCase();
   if (input.startsWith("CONTENT-LENGTH"))
    return(getLength(input));
  }
  return(0);
 }

 private int getLength(String length) {
  StringTokenizer tok = new StringTokenizer(length);
  tok.nextToken();
  return(Integer.parseInt(tok.nextToken()));
 }
}

Figure 17–2 shows the EchoServer in action, displaying the header lines sent by Netscape 4.7 on Windows 98.

Figure 17–2 The EchoServer shows data sent by the browser.

ThreadedEchoServer: Adding Multithreading

The problem with the EchoServer is that the service can only accept one connection at a time. If, for instance, it takes 0.001 seconds to establish a connection but 0.01 seconds for the client to transmit the request and 0.01 seconds for the server to return the results, then the entire process takes about 0.02 seconds, and the server can only handle about 50 connections per second. By doing the socket processing in a separate thread, establishing the connection becomes the rate-limiting step, and the server could handle about 1,000 connections per second with these example times.

Listing 17.20 shows how to convert the EchoServer into a multithreaded version. Section 16.4 (Creating a Multithreaded Method) discusses in detail the process for converting a single-threaded method to a multithreaded method. The basic idea is that the new version's handleConnection starts up a thread, which calls back to the original handleConnection. The problem is how to get the Socket object from handleConnection to run, because placing the Socket object in an instance variable would subject it to race conditions. So, a Connection class, which is simply a Thread with a place to store the Socket object, is used.

Listing 17.20 ThreadedEchoServer.java

import java.net.*;
import java.io.*;

/** A multithreaded variation of EchoServer. */

public class ThreadedEchoServer extends EchoServer
                implements Runnable {
 public static void main(String[] args) {
  int port = 8088;
  if (args.length > 0) {
   try {
    port = Integer.parseInt(args[0]);
   } catch(NumberFormatException nfe) {}
  }
  ThreadedEchoServer echoServer =
   new ThreadedEchoServer(port, 0);
  echoServer.serverName = "Threaded EchoServer";
 }

 public ThreadedEchoServer(int port, int connections) {
  super(port, connections);
 }
 /** The new version of handleConnection starts a thread. This
  * new thread will call back to the <I>old</I> version of
  * handleConnection, resulting in the same server behavior
  * in a multithreaded version. The thread stores the Socket 
  * instance since run doesn't take any arguments, and since
  * storing the socket in an instance variable risks having 
  * it overwritten if the next thread starts before the run
  * method gets a chance to copy the socket reference.
  */
                 
 public void handleConnection(Socket server) {
  Connection connectionThread = new Connection(this, server);
  connectionThread.start();
 }
  
 public void run() {
  Connection currentThread =
   (Connection)Thread.currentThread();
  try {
   super.handleConnection(currentThread.getSocket());
  } catch(IOException ioe) {
   System.out.println("IOException: " + ioe);
   ioe.printStackTrace();
  }
 }
}

/** This is just a Thread with a field to store a Socket object.
 * Used as a thread-safe means to pass the Socket from
 * handleConnection to run.
 */

class Connection extends Thread {
 private Socket serverSocket;

 public Connection(Runnable serverObject,
          Socket serverSocket) {
  super(serverObject);
  this.serverSocket = serverSocket;
 }
 
 public Socket getSocket() {
  return serverSocket;
 }
} 

This server gives the same results as the EchoServer but allows multiple simultaneous connections.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020