On this page... (hide)
For text based browsing there is
If you want a personal web page on the ECE/CIS machines, please post a help-request ticket at http://www.eecis.udel.edu/service. Once space has been allocated, you will access your WWW files under
For acad accounts the URL will be
For more information on HTML (HyperText Mark-up Language), please refer to HTML Beginner's Guide
User cgi scripts are not enabled on the main web servers mentioned above for security reasons. There is a web server available to run CGI scripts on. It is on a separate, untrusted server to minimize security risks. Users are only given CGI space on request.
Requested space will be available at
Note To have a filesystem made on this server to enable you to create/use CGI scripts, use the Computer Service / Help Request system and request access to the CGI server.
There are security issues that you should be aware of when writing your own scripts. Note, that if you have a security hole a CGI that your account on cgi.eecis can be compromised, so special care should be taken, when writing CGIs and in processing any data from them. (This is why CGI scripts are not enabled on the main dept. web servers)
For those who have permissions to update the department websites, the web files can be accessed from any research system.
The Web access logs for our web servers can be found under the directory
An htaccess file provides a method to limit directory and file access to authorized users with username/password pairs. First, create a directory that is mode 755 (or at least readable and executable to
[~/public_html/]> ls -al drwxr-xr-x 4 user group 512 May 18 11:39 . drwxr-xr-x 3 user group 512 Mar 3 09:28 .. drwxr-xr-x 2 user group 512 May 18 11:39 protected
The next step is to create your htaccess password file which will be used for authentication.
NOTE: The htpasswd file you create will contain ENCRYPTED passwords. The default encoding is standard Unix crypt, but MD5 hashes can be used by using the
After you have created the htpasswd file, the next step would be to create an .htaccess file in the directory you wish to restrict access to.
[~/public_html/]> ls -al protected/ total 10 -rwxr-xr-x 1 user group 125 May 18 11:47 .htaccess
NOTE: The .htaccess file and your htpasswd file MUST be world readable. ( mode 644 ), or at least readable by the user httpuser using ACLs, and exist in the
The contents of the .htaccess file ( which protects the entire directory ) are as follows:
AuthType Basic AuthName "My Protected Directory" AuthUserFile /usb/username/public_html/.htpasswd require valid-user
An example of htaccess can be found here.
You can also require that the user use an encrypted session to access certain files. This is good for sensitive or confidential documents which you would not want to send over the network as cleartext. When used in conjunction with the password file you created above, you can allow secure access to only certain users, and certain ip addresses.
To do so, add the following to your .htaccess file (Changing it of course):
<Files secret.txt> SSLRequireSSL require user secure order deny,allow deny from all allow from 128.4. </Files>
In the example above, SSL will be required when accessing the file secret.txt. The required username is 'secure', but any username which is in your htpasswd file can be specified there. Another option is to specify 'require valid-user', which will allow any user in your htpasswd file to authenticate. The 'allow from 128.4.' statement specifies that only users connecting from 128.4.*.* are allowed to access 'secret.txt'. A filemask can also be used in place of a specific file name.
The primary goal of the SSL Protocol is to provide privacy and reliability between two communicating applications. The SSL protocol provides connection security that has three basic properties:
To add a comment, click the link below. You are free to contribute anonymously, but it is preferred that you sign your comments with your name. Simply add