Docsity
Docsity
Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity

Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan

Guidelines and tips
Guidelines and tips
Sell on Docsity
Sell on Docsity
Docsity AI
Docsity AI
Log inSign up

Prepare for your exams

Study with the several resources on Docsity

Find documents

Prepare for your exams with the study notes shared by other students like you on Docsity

Search for your university

Find the specific documents for your university's exams

Docsity AINEW

Summarize your documents, ask them questions, convert them into quizzes and concept maps

Explore questions

Clear up your doubts by reading the answers to questions asked by your fellow students

Earn points to download

Earn points by helping other students or get them with a premium plan

Share documents
download point icon20 Points

For each uploaded document

Answer questions
download point icon5 Points

For each given answer (max 1 per day)

All the ways to get free points
Get points immediately

Choose a premium plan with all the points you need

Study Opportunities

Choose your next study program

Get in touch with the best universities in the world. Search through thousands of universities and official partners

Community

Ask the community

Ask the community for help and clear up your study doubts

Free resources

Our save-the-student-ebooks!

Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors

Implementing an HTTP 1.0 Deamon for Static and Dynamic Web Pages, Study Guides, Projects, Research of Computer Science

Florida State University (FSU)Computer Science

A project for computer science students to implement an http 1.0 deamon that serves static web pages, pages with dynamic content using ajax, and dynamic server pages. The tasks include creating new source code files, testing implementations, and studying ajax programming with xml.

Typology: Study Guides, Projects, Research

Pre 2010

Uploaded on 08/30/2009

koofers-user-4cm
koofers-user-4cm 🇺🇸

5

(1)

10 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Internet Computing
Project 2
Robert van Engelen
Due date: Nov. 27, 2006
Your task is to implement an HTTP 1.0 deamon that serves static Web pages, pages with dynamic
content using Ajax, and dynamic server pages.
To get started:
1. Download the C source code from:
http://www.cs.fsu.edu/~engelen/courses/CIS5930/project2.tar.gz.
2. Chdir to ’project2’ and enter ’make’.
3. Start the deamon with ./httpd 1nnnn, where nnnn are the last four digits of your SSN.
4. Open a browser window with URL http://127.0.0.1:1nnnn
5. If all worked well you should see ’Hello, World!’ displayed in the browser.
The Web server always returns ’Hello, World!’ regardless of the HTTP method (GET/POST) and
URL path. This is too simplistic to be useful. Your tasks are to:
1. Create a new source code file httpfile.c with an implementation of the putfile() function
that takes the current httpd context (httpd struct) and a file path/name (see httpd.h for
the function signature). This function should take a file name as argument, open it, and
copy its content to the HTTP response. The file name is the resourceURI (path) from the
HTTP request header. The putfile() function should also determine the file type from the
file extension to set the Content-Type HTTP header with puthttp(). File types that you
should support are: text/html (.html), text/xml (.xml), image/jpeg (.jpg), image/gif (.gif ),
and application/x-javascript (.js). If the file is not found, you should set the HTTP 404 error
and return EOF. Change httpd.c to call putfile() in the server loop with the resourceURI
(path) if the resourceURI has an extension. If it does not have an extension, it is not a file
and will be considered a dynamic invocation to support Ajax (see below).
2. Test your implementation by entering ’http://127.0.0.1:1nnnn/test.html’ in your browser to
view the ’test.html’ page. You should see the text and image.
3. Modify your httpd.c code (and httpd.h if necessary) to extract and store query strings so
that the resourceURI is split in a path and the query string. For example, the resourceURI
1
pf3

Partial preview of the text

Download Implementing an HTTP 1.0 Deamon for Static and Dynamic Web Pages and more Study Guides, Projects, Research Computer Science in PDF only on Docsity!

Internet Computing

Project 2

Robert van Engelen

Due date: Nov. 27, 2006

Your task is to implement an HTTP 1.0 deamon that serves static Web pages, pages with dynamic content using Ajax, and dynamic server pages.

To get started:

  1. Download the C source code from: http://www.cs.fsu.edu/~engelen/courses/CIS5930/project2.tar.gz.
  2. Chdir to ’project2’ and enter ’make’.
  3. Start the deamon with ./httpd 1nnnn, where nnnn are the last four digits of your SSN.
  4. Open a browser window with URL http://127.0.0.1:1nnnn
  5. If all worked well you should see ’Hello, World!’ displayed in the browser.

The Web server always returns ’Hello, World!’ regardless of the HTTP method (GET/POST) and URL path. This is too simplistic to be useful. Your tasks are to:

  1. Create a new source code file httpfile.c with an implementation of the putfile() function that takes the current httpd context (httpd struct) and a file path/name (see httpd.h for the function signature). This function should take a file name as argument, open it, and copy its content to the HTTP response. The file name is the resourceURI (path) from the HTTP request header. The putfile() function should also determine the file type from the file extension to set the Content-Type HTTP header with puthttp(). File types that you should support are: text/html (.html), text/xml (.xml), image/jpeg (.jpg), image/gif (.gif), and application/x-javascript (.js). If the file is not found, you should set the HTTP 404 error and return EOF. Change httpd.c to call putfile() in the server loop with the resourceURI (path) if the resourceURI has an extension. If it does not have an extension, it is not a file and will be considered a dynamic invocation to support Ajax (see below).
  2. Test your implementation by entering ’http://127.0.0.1:1nnnn/test.html’ in your browser to view the ’test.html’ page. You should see the text and image.
  3. Modify your httpd.c code (and httpd.h if necessary) to extract and store query strings so that the resourceURI is split in a path and the query string. For example, the resourceURI

’http://127.0.0.1:1nnnn/test?course=IC’ has a path ’test’ and a query string with one key- value pair ’course=IC’. The pairs are separated with a ampersand (&) and the strings are URL-encoded. For sake of simplicity we restrict them to be ASCII letters and digits only.

  1. Test your changes by opening ’http://127.0.0.1:1nnnn/test.html?a=b’, which should display the test page by ignoring the query string in the resourceURI.
  2. Create a new source code file httpajax.c with an implementation of the putajax() function that takes the current httpd context (httpd struct), a path, and a query string. The httpd.c server loop should invoke httpajax() when the resourceURI does not carry a file extension. You should take the query string’s ’q’-key value and match it against an array of strings. If the prefix of the value matches a string (case insensitive), then send the string as the HTTP response. You can choose the list of names you want, but use at least a few to test the prefix matching.
  3. Test your implementation by opening ’http://127.0.0.1:1nnnn/test?q=a’. This should display ”Agnes” assuming that the first name that starts with ’a’ in the list is ”Agnes”. Note that the path is not relevant in our example (as long as there is no file extension).
  4. Now on to Ajax. Study form.html and hint.js. Open ’http://127.0.0.1:1nnnn/form.html’. You should get a text entry box. When you enter ’a’ you should see ”Agnes” appear as a suggested name.
  5. Now on to Ajax programming with XML. In the above we just let our server return a string to display. But we cannot handle multiple return values. Multiple return values are to be stored in XML. Modify your list of names, such that each name has an age associated with it. Use an array of structs or two arrays, one with names and the other with ages. Modify form.html, such that there is a line with

    Age:

    . Modify hint.js to get the xmlHttp.responseXML with XML returned by your server and use the DOM to extract the name and age (when present) and to set the ’txtHint’ and ’txtAge’ values using the document DOM. It is up to you how to structure the XML content with the name and age info (remember that you must have one root element and that the HTTP content-type is now text/xml). The putajax() function returns the XML content with the name and only includes the age if the query string matches the entire name. That is, when the query value is ’agnes’ the age is returned with the name (assuming that ”Agnes” is in the name list).
  6. Test your implementation by opening ’http://127.0.0.1:1nnnn/form.html’. You should see the textbox, suggestion, and age. Type ’a’ to see ”Agnes” and type the complete name to see her age.
  7. Now on to dynamic server pages. Create a new source code file httpdsp.c to implement the putdsp() function that takes the current httpd context (httpd struct), a path, and a query string. This function should be invoked by the server loop when the path’s file extension refers to a dynamic server page .dsp, e.g. http://127.0.0.1:1nnnn/test.dsp’. The putdsp() function takes the path and opens the associated .dsp file. The .dsp file is a regular HTML file but also contains server page markup. The server page markup consists of <% and %>, which contains a variable name. Our server page markup is simple, there are no commands just variable names (and no spacing). The variable names refer to the query string keys. Suppose