Jump to content.

Services/ Web

This document describes policies and procedures for the primary webservers for the EECS Department, www.eecs.berkeley.edu and www.cs.berkeley.edu (“the webserver”).

EECS Homepages

By default the webserver looks under /home/eecs/username/public_html to find an index.shtml, index.html, or index.htm file. (Specifically, it uses username’s Unix NIS entry home directory, which may be different than the default by special arrangement).

The webserver is running under Unix and we recommend you set up your file permissions from a Unix host, not a Windows host. See Creating an EECS Homepage for details.

Scripting / Dynamic Content

The primary server www.eecs.berkeley.edu does not support scripts for end-users. However, anyone with a Full IRIS account can run scripts from their home directory from the alternate server apps.eecs.berkeley.edu. The URL would be http[s]://apps.eecs.berkeley.edu/~username.

The server runs scripts using the Apache suexec environment, which enforces a strict security model. Be sure to check the Apache suexec documentation if you are having trouble getting your scripts to work. The most common problem are related to these rules:

At this time the following languages are supported. You script should begin with the proper shebang line to specify the interpreter you want to use.

LanguageFirst line of script

URL Forwarding/Redirection

All requests for URL forwarding or redirection should be e-mailed to help@eecs.

If your account is closed you may have your personal website redirected to an off-site location after the closing date of your account.

Project Web Hosting

There are two pieces of information needed to start having IRIS host your project website:

  1. The location of the files for your website (we recommend using project space for this).
  2. The hostname for your new website (i.e. happy.eecs.berkeley.edu).

Request Hosting

All fields are required.

Personal Information
Website Information

You will receive a response from hostmaster and webmaster about your request. If everything goes well it will be setup and working the next working day. You may want to configure a robots.txt file for your new website.

See also:


It’s hard to find privacy on the web and we do not claim these measures are flawless. Nonetheless, they prove useful enough to document.

  1. Posting complete e-mail addresses on your webpages can be an invitation for spam. Instead, use cgiemail to allow people to e-mail you.
  2. Use a .htaccess file to provide access control for your files and subdirectories. We have examples elsewhere on our website.
  3. meta tags can also stop robots from crawling or indexing a specific page, see Robots and the META element.

See also:

Services Status


Common Tasks