CGS4825, Assignment 5

Due Friday 11/21 at midnight.

Upload copies of httpd.conf, srm.conf, and access.conf

You are to configure your server and get it running. Then do the following

Add the following commands to httpd.conf.

LoadModule webapp_module /home/otter/aul-user-web/libexec/mod_webapp.so
WebAppConnection warpConnection warp localhost:7008
WebAppDeploy /aul/homes/your-user-name/cgs4825/java-servlets warpConnection /cgs4825_your-user-name

Change the permissions on ~/cgs4825 on otter to 705.
Add a directory named java-servlets under your cgs4825 directory on otter.
- Change the permissions on java-servlets to 705.
- Add a WEB-INF subdirectory to java-servlets. Set the permissions to 705.
- Create a web.xml file in WEB-INF.
  - Copy the file web.xml from ~downeyt/cs/public/tomcat
    cd ~/cgs4825/java-servlets/WEB-INF cp ~downeyt/cs/public/tomcat/web.xml .
  - Replace your-user-name with your user name in the web.xml file.
  - Set the permissions to 604.
- Add a classes subdirectory in WEB-INF. Set the permissions to 705.
Restart your Apache server.
You will be asked for a username and password the first time you try to access the cgs4825_your-user-name context through your server. Your usename is your otter username. Your password will be sent to your webmail e-mail account. Do not enter your otter password!
You should now be able to place .class files in the classes directory and run them from the path
/cgs4825/servlet/MyServlet
Create a subdirectory of cgs4825/data named hw5
Create a subdirectory of cgs4825/server named errors
Create the following Aliases in srm.conf
- An alias named /simple to your hw5 directory
- An alias named /all to your hw5 directory
- An alias named /none to your hw5 directory
- An alias named /content to your hw5 directory
- An alias named /errors to your cgs4825/server/errors directory
In srm.conf
- change the HeaderName to HEADER4825.html
- change the ReadmeName to README4825.html
- define the languages that you will use for language negotiation. Remove the ones that you aren't using.
In access.conf, use the Location directive to allow the following features in certain directories. Be sure that only these features are enbaled.
- all
  - allow fancy indexing, but suppress the last modified field
  - allow all options, including content negotiation
- simple: allow simple indexing only
- none: allow no options, not even indexes
- content
  - allow fancy indexing, but suppress the file description field
  - allow content negotiation and indexes
Error Pages
- In the errors directory, create html files for the following errors. Be creative, but the files should load quickly!
  - 403 Forbidden
  - 404 Not Found
- Change the appropriate configuration file so that the above error messages are displayed for the appropriate errors.
In hw5
- Create three different pages for the languages English, Spanish and French. The pages can be simple. The names of the pages should be language.html, with an additional extension for the language. This is the extension defined for enabling language negotiation.
- Create a HEADER4825.html file that contains a hypertext link to language.html. Note that this is a link to a non-existent file. If language negotiation is on, then one of your language files will appear. If language negotiation is off, then a file not found error will appear.
- Create a README4825.html file that contains links to the five URLs
  / /simple /none /all /content
Create a directory index file (it will not be called index.html) in your personal directory that can be viewed by other web servers. Try it out on my student server: otter.aul.fiu.edu:11111
Create a directory index file (it will not be called index.html) in your data directory that will have the following. This page should load when I access yuor server.
- A hypertext link to a file or directory that will create a 403 error. Do not call your error file directly. Have a link to a file that will cause the error page to display.
- A hypertext link to a file or directory that will create a 404 error. Do not call your error file directly. Have a link to a file that will cause the error page to display.
- A hypertext link to /simple
- A hypertext link to /all
- A hypertext link to /none
- A hypertext link to /content
- A hypertext link to a servlet that works. It can be a servlet from a previous homework, or a servlet from the book's web page. Modify the servlet so that it will be in a package named hw5.
- A hypertext link to your personal page. There should be a a directory index file in this directory.
- A hypertext link to my student personal page, /~tdowne99, through your server.

Use the directory index file to investigate what happens when you access each directory and try the language.html link

Notice when content negotiation works.
Notice when fancyindexing works. Are some fields suppressed?
Notice when error pages appear. Are they your error pages?
Notice where the header and readme files appear.
Have fun.

Check my student server for an example of what the assignment looks like: otter.aul.fiu.edu:11111