The World Wide Web (WWW) is a
way to access and distribute information on campus and around the world
on the Internet. Our main web server is at www.uky.edu and the complete
(uniform resource locator) is:
University departments, faculty, classes, and organizations, including
registered student organizations, can have space on the campus server.
(Individual students can have web pages on the student web server -
for more information.)
There is no charge for this service, but if your disk space requirements
will exceed a few dozen megabytes, please let us know. The web server
does not have the resources to act as a general file server, archive, or
backup! When the amount of available disk space on www.uky.edu becomes
low large files will be arbitrarily erased without notice.
Your use of the University's web servers must conform to the University's
and like all University computing resources, must comply with the
To become a web information provider you must request a web userid (a
U-connect userid won't help) from user account services at the
in McVey Hall.
Each person who will be working on files on the web server must have
their own web userid in their own name issued to them by user accounts
University computing policy
generally prohibits sharing userids or passwords. The purpose of a web
userid is to identify and authenticate an individual person with access
to the server and not to define a URL.
To provide information for the web server you may need at least a little
familiarity with Unix. You can do your editing and preparation on any
system you prefer (Mac, VM/CMS, Windows, etc.), but the files will
eventually be put on a Unix system and you will need to be able to use
FTP (File Transfer Protocol) or log on there and use a few commands to
prepare them for use by the server.
The recommended and supported web browser at the University of Kentucky
which is available for Macintosh, Unix, and Windows systems. Microsoft
Internet Explorer is also widely used on campus. Other browsers are also
in use as well and you generally shouldn't use non-standard,
Our web server is Apache running under Unix. It does not support
Microsoft's Active Server Pages (ASP). PHP and Python are available.
We cannot support or recommend the use of any web page creation tools or
HTML editors, such as Dreamweaver, Adobe Pagemill, Microsoft Front Page,
Netscape Navigator Gold, etc., and we do not provide any server code
that they may require. You can use these products with our server if you
desire and can do so without assistance from Information Technology. Even
server extensions that are available without charge would require
maintenance by our staff and can unnecessarily complicate the work of
our web providers who choose not to use them, therefore we do not make
Departmental and Other Campus Web Servers
Some departments, colleges, and other organizations operate their own
web servers (a recent survey located over 200 web servers on campus).
We have no control over those servers or their contents, but we do have
links from pages on www.uky.edu to other campus servers when
appropriate. If you maintain pages for your organization on a server
other than www.uky.edu and we have links to them (in the
for example), please inform us (by e-mail to firstname.lastname@example.org)
when a URL changes. Note that all University web servers must conform
to the University's
You will need to learn some Hypertext Markup Language (HTML) - the
language of web pages. A number of tutorials and references are
available from the web. We provide a very simple
skeleton HTML file
that is suitable for departmental use.
at email@example.com for information about HTML classes.
Information for the web server is kept in files on the system at
www.uky.edu. When you connect to www.uky.edu with your id and password
(using SSH or FTP, for example), you should find in your default
directory a subdirectory called "www" for your web files. (If a www
subdirectory isn't already there, you can create one using your FTP
client software or the Unix mkdir command.) You will put files for use
by the web server in your www directory using FTP or whatever method
that works best for you. You must make these files available to the
server by setting the file access flags (the server system is set up to
do this by default, but you should check to be sure they are correct).
For example, on a Macintosh you would use Fetch, an FTP client,
to copy files from the Mac to the web server. When you start Fetch
you will see a connection dialog in which you will specify the
name of the server (www.uky.edu), your web userid, your password,
and the directory on the server (www for your personal space or
the directory path assigned to your project). Windows users might
use an application like Ws_ftp.
Files copied by FTP to the server are made globally readable by
default. This is necessary to make them available via the web
server. You may need to adjust the file access permission settings
for some applications or to make them available for
Fetch has functions under the Remote menu to control the access
permissions for your files on the server. (It also allows you to
erase and rename your files as needed.) Most FTP clients also
support the site umask command for controlling access
permission settings. You can also SSH to the server, log on, and
use the chmod command for this.
Generally you will want your HTML files to be readable by everyone and
writable only by the owner. If you have a group working on files you may
need the group write setting too. Any subdirectories generally will
also have these settings. The FTP command site umask 022 will
make these settings on files when they are uploaded.
In addition, subdirectories need to have the search/execute
authorization set for everyone so the web server can search
them for files. Individual files don't need the search/execute
authorization unless you are using the server side include
feature (see the
Apache server documentation
for more information).
Software is available on some systems that will allow you to use
tools you are more familiar with for editing your HTML files and
move them more-or-less automatically to the server. BBedit
on the Macintosh and the Xftp command on VM/CMS are examples.
Keep in mind that the Unix file system is case sensitive. For
example, the names "Sample.html" and "sample.html" are not equivalent
and don't refer to the same file. The usual convention is for HTML
files to be named with .html at the end, but .htm works too (except
for your initial "welcome.html" file). Other common endings are .gif
for GIF (Graphics Interchange Format) images and .jpeg for JPEG (Joint
Photographic Experts Group) format images. In a departure from the
Unix custom, these suffixes are not case sensitive in that both .GIF
and .gif would be recognized as a GIF file, but a URL must still match
the case actually used to locate the file.
We are running with the Apache server's CheckSpelling option enabled. If
a URL specifies a file or directory that doesn't exist the server
attempts to find something with a similar name. This means that the case
specified in the URL need not be correct. This search incurs additional
overhead on the server and requires an additional exchange between the
browser and server, so you should make sure links included in your pages
are correct, but it does significantly ease finding things for someone
typing a URL at their browser. This can also inadvertently reveal
sensitive files so you may want to disable it for some subdirectories.
Create a file called .htaccess in the subdirectory and include the
CheckSpelling Off directive. Consult the
for more information.
Once you have loaded your files you can reference them for testing from
your web browser with a URL like this:
where "~userid" is a tilde followed by your userid and "typical.html" is
the file in question. If you don't specify a file the server will look
for one called "welcome.html" by default and you should use
"welcome.html" for your initial page (note that "welcome.htm" won't
Note that tildes are not legal characters in URLs according to the
standard, but they are widely accepted nonetheless. To comply with the
standard you should use the sequence %7E instead of a tilde:
Don't advertise a URL on www.uky.edu using the ~userid form
for other than testing, class, or personal purposes! This is very
At some point in the development of your web project get in touch with
us and we will set up a more permanent directory and URL for your
publication-quality files leaving your www directory for testing and
development. This arrangement facilitates the maintenance of the server
and helps assure that your files will be handled correctly in the
Once you have pages ready to publish, contact firstname.lastname@example.org
and tell us the project you are working on, your department, the web
userid or userids that will be used, and a phone number where we can
There is a mailing list for campus web providers - WebPubs-L. To join
send a note to email@example.com with the following as the text:
subscribe webpubs-l Your Name