Web Page Guide

HOME

Client Services

Client Links

Tech Support

Other IGS Sites

Community Links

Media Links

Other Links

Searching the Net

Guestbook

Webring

Web Page Guide

Table of Contents

Introduction
This document is designed to help users of IGS set up personal web pages. It will tell you where and how to set up your web page directory, and offer suggestions on how to upload your files to the server.

This document is not intended to teach you about the World-Wide Web in general or to teach you how to write HTML (Hypertext Markup Language) code. Pointers to such information are given at the end of this document.

Please read this document and follow the instructions carefully.

Table of Contents

Policies
Who can have web pages? All customers of IGS Northumberland with personal accounts are permitted to have personal web pages free of charge. You must ask info@phc.igs.net to create an account for you on the web server.

Commercial advertising is not allowed on personal web pages. If it is your intention to advertise products or services or to promote any for-profit organization, please contact IGS (info@phc.igs.net) about commercial web services.

If you would like a link from the IGS Northumberland home page (which is already advertised on most WWW directories and search engines) to your personal home page, we ask that you include a link from your home page back to ours. Visit the Client Links Pages for more info

These policies are subject to change without notice.

Table of Contents

Uploading Your Documents
The easiest way to update your web pages is to edit them on your own computer and upload them to the web server using FTP (the File Transfer Protocol).

If you are using Windows, the FTP program recommended by IGS is called WS_FTP. In WS_FTP, you can make uploading your web pages easier by creating a new Session Profile. In WS_FTP's Session Profile window, just click on the New button and fill in the form as follows:

    Profile Name:  IGS Web Server
    Host Name:     phc.igs.net
    User ID:       <USERNAME>
    Password:      <PASSWORD>
    Initial Directories
       Remote Host:   ~/.public_html
       Local PC:      <LOCAL dir>

Here is an example from my machine:

     Profile Name:  IGS Web Server
     Host Name:     www.igs.net
     User ID:       rene
     Password:      ********    (Did you think I was going to tell you?)
     Initial Directories
             Remote Host:   ~/.public_html
             Local PC:      c:\web

Once you have set this up, click Save to keep the session profile.

Anytime you want to upload your pages, select the "IGS Web Server" session profile and click OK. Then, transfer the files by selecting them on the left side of the screen and clicking on the right arrow between the "local system" window and "remote system" window.

Your files must have proper file extensions. For example, HTML files must end in .htm or .html, GIF files must end in .gif, and so on. Unix filenames are case sensitive, so the file extensions must be in lowercase. Also, binary files, such as GIF and JPG files must be uploaded in binary mode and ASCII text files, such as HTM, HTML, MAP and TXT files, should be uploaded in ASCII mode.

Your default, or main, home page should be called "index.htm" or "index.html".

Table of Contents

How the Public Will Access Your Web page
The URL's for your web pages will be as follows:

      
http://www.phc.igs.net/~<username>/<pathname>

Here are some examples:

 http://www.phc.igs.net/~rene/
  ... will access a default page,  ~rene/.public_html/index.htm

http://www.phc.igs.net/~rene/bookmark.htm
       ... will access ~rene/.public_html/bookmark.htm

http://www.phc.igs.net/~rene/tree.gif
       ... will access ~rene/.public_html/tree.gif

http://www.phc.igs.net/~rene/radio-tv/my-radio.htm
       ... will access ~rene/.public_html/radio-tv/my-radio.htm

For More Information

HTML (Hypertext Markup Language):

World Wide Web URL's:
 http://www.boutell.com/faq/#authoring
 http://www.netscape.com/home/how-to-create-web-services.html

HTML Editors -- See the Auxiliary Winsock Utilities List...
 http://uts.cc.utexas.edu/~neuroses/utils.html

World-Wide Web FAQ (Frequently Asked Questions):
 http://www.boutell.com/faq/

Table of Contents

Adding a counter to your page
You can add a counter to your page using one of the following HTML commands:

For cardinal numbers (1, 2, 3, etc.)...
```

```
For ordinal numbers (1st, 2nd, 3rd, etc.)...
```

```

VERY IMPORTANT! Any page should contain no more than one counter reference.

Table of Contents

Setting up Imagemaps

To set up an imagemap, simply make your image a link to the map file and add the "ISMAP" option to the image tag.

Here is an example of some HTML code which assumes that the map file and image file are in the same directory...

<a href="test.map"><img ismap src="test.gif"></a>

NOTE: IGS uses the NCSA mapfile format. The CERN mapfile format does NOT work on the IGS server.

Table of Contents

Forms
Using HTML, you can create forms that net surfers can fill out online. This section does not explain how to create forms, but rather how to make the system send the information filled in the form to you via email when the user presses the "submit" button.

To use the IGS-provided "mailto" script to send form results to you via email, use the following as your "FORM" tag:

<FORM METHOD="POST" ACTION="/cgi-bin/mailto.pl">

You will also need to include a few hidden fields in the form so that the mailto script will know where to send the mail:

The "from" field should specify the address from which the email message will be coming. You may choose to have this as a visible field to allow the visitor to your page to fill in their own address. As a hidden field, you may have it set to "www@phc.igs.net", so that you'll see immediately that it is a submission of your form.
The "to" field should contain your email address (or any other that you would like all of the form submissions to go to).
The "body" field should contain a header line for the email message. For example, "The form contained the following fields:".

John Slade, an IGS customer, has written a document on Form Processing at IGS to help other users get started. If you can't get your form working from our document, you should find John's useful to overcome any problems!

Table of Contents

Setting up your own CGI Programs
NOTE: This is an advanced feature, and you should only attempt to use it if you:

know what a "cgi-bin" is
think you can learn how to create directories and change file permissions on a Unix system
have at least a limited amount of programming experience.

Free technical support from IGS will NOT be provided for this feature.

Create a subdirectory within your .public_html directory called "cgi-bin". Place any cgi-bin executables in that directory. If your cgi-bin is a script (such as Perl or one of the Unix shells), make the script executable using the chmod command in Unix. For example:

chmod a+x scriptname

Making the script executable can also be accomplished through WS_FTP by using a "site" command. Right-click on the word "Binary" near the bottom of the WS_FTP window. The FTP Menu will come up. Select "FTP Commands", then "SITE" and enter the necessary chmod command.

Your scripts must be referenced via the "cgiwrap" program. Here is how you do it:

http://www.igs.net/cgi-bin/cgiwrap/<username>/<scriptname>

Here is an example:

http://www.igs.net/cgi-bin/cgiwrap/rene/myscript.pl

If your script is not working and you would like to see some debugging output, substitute "cgiwrapd" for "cgiwrap", like the following:

http://www.igs.net/cgi-bin/cgiwrapd/rene/myscript.pl

Support is also available for NPH (no-parse-header) scripts, by substituting "cgiwrap" with "nph-cgiwrap" or "cgiwrapd" with "nph-cgiwrapd".

Table of Contents

Password protecting a directory
To password protect all documents in a certain directory on your web site, you need to create two files.

The first, called ".htaccess" (don't forget the dot at the beginning), must reside in the directory being restricted. It is formatted as follows:

AuthUserFile /usr/home/username/.htpasswd
AuthGroupFile /dev/null
AuthName "My Secret Page"
AuthType Basic

<Limit GET>
require user jim
require user bob
require user jane
</Limit>

The above .htaccess file would restrict access to the users "jim", "bob" and "jane". These have no correlation to their username on the system to which they dial in; you are creating these "user accounts".

The AuthUserFile directive allows you to specify the password file (the file in which the users' passwords will be stored). Preferably, this file should be located outside of the restricted directory.

Set the AuthName directive to the title of the directory. In the example above, someone trying to access would see "Enter username for My Secret Page at www.igs.net".

Leave the AuthGroupFile and AuthType directives as they are.

Between the <Limit GET> and </Limit> directives, each line lists one user (who presumably would also be listed in the password file) who has access to the directory.

To add users to the password file, use the command "htpasswd". When you enter the first user, you will have to tell htpasswd to create the password file using the "-c" command-line option.

For example:
"htpasswd -c /usr/home/rene/.htpasswd jim" to start the password file /usr/home/rene/.htpasswd, with jim as the first user.

Add more users to the password file the same way, but make sure to leave "-c" out, otherwise you will delete the previous users!

For example, to add jane to the password file, type "htpasswd /usr/home/rene/.htpasswd jane". The htpasswd program will ask you for the password to set.