Once the InterNIC announces that your domain name has been registered (or transferred, if applicable), it usually takes about 2-5 days before it is active. All internet providers must update their records (DNS tables) to reflect new site locations. This is called propagation.
Who is the InterNIC? Click here for a link to their site.
We recommend that you use, Submit-it!. This site allows you to enter your information one time and then submit to the many of the major search engines; however, a fee may be required. We have our own submittal service for our clients that have enrolled after March 15, 1997. We also have posted a complete list of the search engines and indices to which we will submit your site.
What if you want your site ranked higher on the search engines, especially a large search engine? We recommend following the strategies described at the Rank This! website.
If you are looking for a Graphic Analysis Program we suggest "Virtual Webtrends".
"Virtual WebTrends" is a Web Server
Traffic Analyzer specially designed for Web Servers that are hosted on remote sites -
often called Virtual Web Servers.
Virtual WebTrends is a derivative product of the award-winning WebTrends software and
includes the same powerful analysis engine and report capabilities.
Virtual WebTrends is designed to retrieve log files that are located on remote systems
using an HTTP URL. Once Virtual WebTrends retrieves the log file to your local system
subsequent analysis requires only the transfer of the data between your local file and
remote file. Virtual WebTrends identifies any changes in the log file, and automatically
retrieves only the new information before it starts the analysis.
Virtual WebTrends is designed with ease of use and speed in mind allowing you to get
essential reports with minimal effort. Wizards, On-Line Help and Free Technical Support
are part of the Virtual WebTrends package which is priced at only $79.
Buying Virtual WebTrends is easy! Just download the 14-day free trial, and you will have
the option to purchase Virtual WebTrends On-Line from WebTrends directly.
| Virtual WebTrends is a powerful log analysis program and is available from: |
 |
Your log files contain the statistics for your site's traffic. These files are in your /logs directory. The raw files mat be large and difficult to understand. We suggest using a log analysis program to present these statistics in a more graphic format. We have provided a file called usage.html which has some of your sites stats compiled in list format.
We have instituted a new system for the management of log files, as of 27 March 1998. Please click here for a description of the new system
If you have had us add Frontpage extensions to your site, we may need to add an alias to our root configuration file for you to be able to view your logs. Just let us know if this problem arises and we will be glad to correct it.
T
he main databases available on our system are mSQL and mySQL . They can be accessed via PHP (probably the most widely used method) or via the mSQL prompt via telnet (If you want to try this, get the mSQL docs first!).Note: E-Brewer.Com offers mSQLand mySQL databases as a free service to our premium customers. We do not provide tech support for databases; however, we have excellent tutorials on our site regarding mSQL and PHP.
Although our networks incorporate many different machines with varying software and features, the majority of our accounts are on UNIX servers. Listed below is some of the more commonly requested information.
Hardware: CPU is a Pentium Pro 200 w/128 megabytes of RAM
4.2
Gigabyte Hard drives on Ultrawide SCSI (most have 2)
100
Mbit/s Network Interface Cards connected to multiple, redundant T-3 lines provided
through Savvis, UUNet and GoodNet w/ autonomous routing
Software:
Operating sytem is: BSDi 2.0.1
Webserver
is: Apache Stronghold 1.3.0
'C'
compiler is: GCC 2.5.8
NCSA,
Ncurses/Gdbm
Perl
interpreter is: perl5.00404
path
is /usr/local/bin/perl
SMTP
is:
sendmail 8.9.1
path is /usr/sbin/sendmail
Databases
available: mSQL 1.0.16 and MySQL 3.2.1
Also
available: PHP2, PHP3.0.2a, Imagemap, cgiemail
Frontpage
2.0('97) and 3.0('98)
Guestbook,
WWWBoard, SimpleSearch
mreply
(autoresponder), pine (telnet mail)
JAVA
(pre-compiled, no JDK on server)
Guestbook allows you to set up your own comments page. From there, visitors can add entries to your guestbook and they will be displayed with the most recent at the top and scrolling down or vice versa. Other options include the ability to limit HTML in the entry, link to e-mail address with mailto tag, use a log to log entries, redirect to a different page after signing, e-mailing whenever a new entry is added and much more.
Note for Non-Virtual Domain accounts: Non-Virtual accounts do not have telnet access; therefore, such accounts do not have the capability to install these scripts using our administrator. You can however install this script by downloading it directly from the author and following the README file.
Download From Matts Archives: http://worldwidemart.com/scripts/
Note for FrontPage users: You do not need to use this script, although you may use it, if you wish. You can also use the FrontPage Discussion Web Template. If you decide to use our installation script, you will need to contact us, to request that we setup what is called an "Alias" for your "guestbook" directory. You will also need to move your "guestbook.cgi" file into the "cgibin" directory. Finally, you will need to change the path referenced in "addguest.html" for the new location of the "guestbook.cgi" file.
There are two ways that you may install the Guestbook script:
To run the installation script, you will need to connect to your site via telnet. Once at the telnet prompt, type the following command:
For example, if your domain name is "xyz.com", and your email address is "john@doe.com", you would type:
Please note the spaces between the words.
NOTE: Over the past few months we have started to change the way we set up new sites. Some directories may not be where they are on older sites. We will be publishing a comprehensive map of how sites are laid out in the near future. We will also be re-writing the makeguest program to account for these changes. We should be done by the end of October.
After the installation script finishes, you may customize the files to your delight.
It is that simple!
WWWBoard is a threaded World Wide Web discussion forum and message board, which allows users to post new messages, follow-up to existing ones and more.
Note for FrontPage users: You do not need to use this script. Instead, you should use the FrontPage Discussion Web Template.
Newer sites will have the WWWBoard installed off of their Home directory by default. There will be a symbolic link in your DocumentRoot (the directory your web pages go in) that makes the wwwboard reachable as:
http://yourdomain.com/wwwboard
If you have an older site or your wwwboard directory has been removed, you can download the program from Matt's Script Archive and install it by hand - OR - you can use our automatic install program.
To download the program, go to:
To run the installation script, you will need to connect to your site via telnet. Once at the telnet prompt, type the following command:
For example, if your domain name is "abc.net", you would type:
After the installation script finishes, you may customize the files to your delight. You will find a wwwboard directory in your Home Directory. This is where you are initially placed when you login vie telnet. Your DocumentRoot directory will probably be www or wwwfp if you have Frontpage installed on the site. To make the wwwboard directory visible to it, use these commands:
cd www <enter>
ln -s ../wwwboard <enter>
It is that simple!
If you wish to run more than one message board, follow these directions:
1. Log into your root directory via telnet.
2. Create the directory that will house the wwwboard:
(example)
mkdir bob
3. Run the install script:
makeboard
yourdomain.com bob
4. If you wish, edit the html code of the index.html page in the
/yourdirectory/bob/wwwboard directory to reflect the information
you want shown on the board.
cd bob/wwwboard
pico index.html
5. If you wish, place a symbolic link in the bob directory that points to the wwwboard:
cd bob
ln -s wwwboard/index.html
To create a second wwwboard, follow these steps:
1. Go back to your root directory.
cd /mnt/web/guide/yourdomain
2. Create the directory that will house the next wwwboard:
mkdir bob2
3. Run the install script:
makeboard yourdomain.com bob2
4. If you wish, edit the html code of the index.html page in the
/yourdirectory/bob2/wwwboard directory to reflect the information you want shown on the
board.
cd bob2/wwwboard
pico index.html
5. If you wish, place a symbolic link in the bob2 directory that points to the wwwboard:
cd bob2
ln -s wwwboard/index.html
You now have two messageboards: one for bob, and one for bob2.
For information explaining the background of the Year 2000 issue, we recommend that you visit a frequently-asked questions page on the Microsoft site.
Most of the servers owned by E-Brewer have the UNIX operating system. The remainder of our servers have the Windows NT operating system. Please review the categorized information below for links to relevant compliance information.
Your site is located on an UNIX machine unless you have specifically asked for NT.
The UNIX operating system uses a different date-keeping method than that used by those computers affected by the two-digit date issue. The UNIX operating system counts the number of seconds since the UNIX epoch in order to determine dates (the UNIX epoch was on midnight, January 1, 1970).
All custom scripts that E-Brewer has developed gather any "date" information in UNIX format, therefore Y2K is not any issue for any of our scripts.
| Operating System: UNIX BSDi 2.0.1 | Link: BSDi Website |
| Server Software: Apache 1.2.5 | Link: Apache.org Website |
| 3Com and DLink 10/100 hub | Links: 3Com Site, DLink Site |
| Bay Networks 350T 10/100 switch | Link: Bay Networks Site |
| Cisco 2500, 4000, and 7200 series router | Link: Cisco Site |
| Operating System: Windows NT 4.0 with Service Pack 3 | Link: Microsoft site |
| Server Software: Internet Information Server 4.0 | Link: Microsoft site |
| 3Com and DLink 10/100 hub | Links: 3Com Site, DLink Site |
| Bay Networks 350T 10/100 switch | Link: Bay Networks Site |
| Cisco 2500, 4000, and 7200 series router | Link: Cisco Site |
To modify an existing HTML form to work with the script cgiemail you will need to use the following form action within your HTML code:
<form method="post" action="/cgi-bin/cgiemail/mailform.txt">
Please Note: If you are a FrontPage user with the FrontPage 98 extensions installed on your site, you will use this path instead:
<form method="post" action="/cgibin/cgiemail/mailform.txt">
(The difference is that you are using "cgibin" instead of "cgi-bin".)
This code calls the preinstalled script cgiemail which is in the server's cgi-bin directory once the web page visitor clicks the "submit" button. The script cgiemail in turn calls a text file (or template) called mailform.txt. The template defines the format by which the submitted form content is to be sent via email.
You can create the template in a basic text editor (such as MS Notepad) beginning with the following two lines:
To: username@yourdomain.com Subject: Information Request
Substitute the desired recipient email address and subject above. If your form asks for the email address of the visitor (be sure to name this field: email), add this as the second line of the template:
From: [email]
There can be no blanklines at the top of the file and no blank spaces at the beginning of these header lines.
Next, you will need to add ALL field names within the HTML form to the template in a form similar to the following:
To: username@yourdomain.com Subject: Information Request Name [name] Address [address] Phone [telno]
As long as each form field name is contained within brackets ("[ ]") within the template, the email should be sent successfully and contain all submitted data. We suggest using all lowercase field names within your HTML form and template.
If you want a specific web page to load when the email is successfully sent, such as a thank you note, add the follow code to your HTML form:
Substitute the URL of the file you wish to load after form data is submitted. The field name in this case MUST be "success", but does not need to be added to the template.
<form method="post" action="/cgi-bin/cgiemail/mailform.txt">
<form method="post" action="https://wwwXXXX.E-Brewer.com/cgi-bin/cgiemail/<yourdomain>/mailform.txt">
where XXXX should be substituted with the number of your server.
<form method="post" action="https://wwwXXXX.E-Brewer.com/cgi-bin/cgiemail/<yourdomain>/frontpage/mailform.txt">
where XXXX should be substituted with the number of your server.
IMPORTANT THINGS TO REMEMBER:
<form method="post" action="/cgi-bin/cgiemail/mailform.txt"> the mailform.txt file is in your root directory
<form method="post" action="/cgi-bin/cgiemail/forms/mailform.txt"> the mailform.txt file is in directory called forms
Try our test email form.
See the source of the testform.txt template.
Our webform.cgi tutorial shows how to setup an HTML form to send email upon the submission of the form data. The code calls the preinstalled script webform.cgi, which is in the "cgi-bin" directory of the server, once the web page visitor clicks on the "Submit" button. This program is a derivation of the formmail.cgi program available at Matt's Script Archive.
To modify an existing HTML form to work with webform.cgi, please follow the simple instructions below.
We will use the example of an account with E-Brewer
with the following
account info:
Homepage name: index.htm
Name of page with the form on it: xyz.htm
Name of the thank-you page: thanks.htm
Email address: abcdefg@xyz.com
First, we will need to make a link to "xyz.htm" from the homepage, "index.htm". The link will need to use this piece of HTML code, inserted into the file, "index.htm":
We can of course substitute other words or an image for, "Link to form page."
Second, we need to insert some HTML code into the file, "xyz.htm".
We will insert this code:
Of course, we may we may replace "Form
Submission" with some other subject.
For Secured Server on UNIX the path would be:
<form method="post" action="https://wwwXXXX.E-Brewer.com/cgi-bin/webform.cgi">
<input type="hidden" name="recipient" value=" abcdefg@xyz.com">
<input type="hidden" name="redirect" value="https://wwwXXXX.E-Brewer.com/yourdirectory/thanks.htm">
<input type="hidden" name="subject" value="Form Submission">where XXXX should be substituted with the number of your server.
FrontPage97 users should follow a different tutorial. Please click here.
It is recommended that FrontPage98 users use a FrontPage-based form instead. The FrontPage98 Form WebBots have much greater functionality. For more info, click on the word, "Help" on the menubar of FrontPage Editor. Then select "Microsoft FrontPage Help". Click on the "Index" tab. In the box, type "form". You will see a list of relevant topics.
E-Brewer can setup a form for you for a one-time $30 fee. Each form would entail such a one-time fee. You would need to specify:
the email address to which the form submission would go
the name of the thank-you page
all the categories of boxes for the visitor to fill in
Please note that our work would entail the basic structure of the form itself rather than the aesthetic design of the page. The customer would be responsible for the aesthetics, after the form is setup. We will, of course, give the form an organized design.
If you are interested in this service, please contact our Sales Office toll-free at 1-888-932-2010. For international callers, please use our standard line at 407.772.0454. Alternatively, you may order this service by filling in our on-line A La Carte Order Form.
Our servers have the capability to run CGI scripts
based on Perl, Unix SH, BASH, KSH, CSH, and C/C++ languages. Perl is a our language of
choice for most applications as it is a world standard and is well suited to CGI. In
addition, Perl code does not require manual compilations whereas C/C++ code must be
compiled on our web servers prior to use.*
If you have a custom CGI script that you need to use, simply upload it to your personal
"cgibin". Here are some helpful tips to follow when installing Perl scripts:
Utilize any directory except "cgi-bin" for your own scripts.
We recommend placing them in your cgibin directory to help consolidate them.
Upload in ASCII transfer mode (and NOT BINARY mode)
Those using Fetch should use Text mode (not Raw Data)
The first line of each script should read: #! /usr/local/bin/perl
(please also see below)
One exception is if you are using PerlShop, it should read:
#! /usr/local/bin/perl5.003
Reference the script using "cgibin", NOT using "cgi-bin"
Use ".cgi" extensions for all scripts
If a script calls another file within your account, but the script does NOT
require a URL, you need to use the system path.
/web/guide/<domainname>/...
<- if file resides in root
/web/guide/<domainname>/cgibin/...
<- if file resides in cgibin
Substitute the path to the file beginning with your domain name. Your domain name is the
directory name of your account.
Long Winded
Really
Long Winded
/usr/local/bin/perl5.001
/usr/local/bin/perl5.002
/usr/local/bin/perl5.003
/usr/local/bin/perl5.00307
/usr/local/bin/perl5.00404 = /usr/local/bin/perl
chgrp bbsuser file.cgi
This is typed at the telnet prompt from within the /cgibin directory. (Click here for a telnet tutorial.)
chmod 755 file.cgi
chmod 644 file.shtml
http://www.apache.org/docs/mod/mod_include.html
perl -w file.cgi
#!/bin/sh echo Content-type: text/plain echo echo 10 print "HELLO" echo 20 goto 10 echo Hello there I see you saw my page at $HTTP_REFERER echo You are using $HTTP_USER_AGENT as a browser. echo $HTTP_USER_AGENT >> agentfile.txt echo \<a href=\"http://mydomain.com\"\> Home \</a\>
Yawn - Notice the \ escapes, the blank echo after the content-type line. Also If you want to use agentfile.txt line, I had to upload a blank file called agentfile.txt, and then use the file manager to set PUBLIC WRITE on that file. Or the script will not work! (telnet: touch agentfile.txt;chmod o+w agentfile.txt)
Galaxy's CGI- Common Gateway Interface
- Lots of information on CGI scripting, and the longest URL on the Web, including
pointers for more information on image mapping, etc.
Julia
Martinson's Collection
- a great collection of information on CGI & HTML.
O'Reilly & Associates
- Don't normally recommend books, but in the case of Perl, Unix, Linux, Scripting,
etc. your might need to read-up with the best.
The Common
Gateway Interface
- An introduction (with examples) to CGI scripting. One of the best sites.
Shareware
CGI Scripts
- Consists of scripts for Guestbooks, Forms, and Counters. Includes some Apple
programs as well.
FeLIpe's Applescript CGI
Examples
- An Apple reference to CGI-Scripting with examples. We're not Mac-users at E-Brewer,
so I haven't tested this site out. Mac people, let us know what you think.
CERN HTTPD
- Resources for image-mapping, scripts, forms, search engines, CGI, etc. Please note
that this is not our server, though similar, and some of the steps (BIN
references) are different. Please refer to our FAQ for specifics on this.
Accessory Scripts-
CERN
- Reference for forms submissions, etc. Again, the references are going to be slightly
different for our server and please refer to our FAQ documentation for the changes needed.
The processing of CGI
arguments under TCL
- More information on CGI.
Accessory Scripts-
CERN
- Reference for forms submissions, etc. Again, the references are going to be slightly
different for our server and please refer to our FAQ documentation for the changes needed.
Imagemap Help Page
- Imagemaping made simple in an easy to follow guide.
HTGREP
- if you need a searchable index, this is supposed to do the trick. I haven't messed with
it yet, though.
NASA's 'Information on
Search Tools'
- a interesting page with many ideas on solving local searching problems.
PERL
- A great language to learn in the generation of dynamic documents (on-the-fly page
creation) such as forms.
You can set up unlimited e-mail aliases for email addresses which
are to forward to an
address other than your POP3 mailbox. Instructions on this subject are found on this
page. Instructions on configuring your mail program are available elsewhere on our site.
First, someone sends mail! The address on the mail is foo@bar.com.
The user foo and the domain bar.com physically exist on our number X server. Because of
how DNS routing works (completely different discussion), the mail message is routed to the
appropriate server, good old number X. Our configuration files then decipher that the mail
for domain bar.com goes to local user foo. In the truest sense, this user is
foo@wwwX.E-Brewer.com, but because of the virtual domain configuration, it can appear as
foo@bar.com. Just make sure to use your Local ISP as the SMTP server.
Next, our server checks the home directory for the user foo. What it is looking for is
further instructions on routing the mail message. The first thing it will look for is the
".domains" file as a means of having 'virtual users' for your domain. It is not
elaborate by any means; it is just effective.
Sample .domains file:
info@bar.com #
list-request@bar.com #
foo@bar.com foo
root@bar.com root@shaver.com
questions@bar.com joe@somewhereelse.com
other@bar.com jim@other.net
bar.com jim@other.net
IMPORTANT: Please read the following information :-)
Now say you want forward some of the mail, from bob@bar.com to bob@aol.com, the .domains file would look like this:
BEFORE |
AFTER |
| info@bar.com # list-request@bar.com # foo@bar.com jim2 root@bar.com root@E-Brewer.com jim@bar.com jim bar.com jim |
bob@bar.com bob@aol.com info@bar.com # list-request@bar.com # foo@bar.com jim2 root@bar.com root@E-Brewer.com jim@bar.com jim bar.com jim |
Now say you want forward some of the mail to different addresses, from bob@bar.com to bob@aol.com and to bob@mci.net. The .domains file would look like this:
| BEFORE | AFTER |
| info@bar.com # list-request@bar.com # foo@bar.com jim2 root@bar.com root@E-Brewer.com jim@bar.com jim bar.com jim |
bob@bar.com bob@aol.com,bob@mci.net info@bar.com # list-request@bar.com # foo@bar.com jim2 root@bar.com root@E-Brewer.com jim@bar.com jim bar.com jim |
Please note that in the above example, there are no spaces before or after the comma on the top line.
Now say you want all mail that is sent to your domain (except for foo@bar.com) forwarded to you local ISP mailbox, the .domains file would look like this:
BEFORE |
AFTER |
| info@bar.com # list-request@bar.com # foo@bar.com jim2 root@bar.com root@E-Brewer.com jim@bar.com jim bar.com jim |
foo@bar.com jim2 jim@bar.com jim@earthlink.net bar.com jim@earthlink.net |
To Forward all mail without exception, simply remove the foo@bar.com jim2 line, leaving only the last two lines.
To retrieve email from your POP3 mailbox, you must first setup your mail program to access your mailbox.
Important Note: Your mail will not work until you domain is fully registered and working.
The POP3 Account
Use the following settings to configure your mail program to access the master POP
account:
POP3 Server: (Use your domain name.)
SMTP Server: (Use the SMTP server provided by your ISP. If we are your ISP, use your
domain name here as well.)
(IMPORTANT: Customers Use "www?.E-Brewer.com" As Your POP3 Server)
Please click on one of the following links for instructions on the setup of particular email programs:
 |
Netscape Navigator 3.0 Instructions | Outlook Express Instructions |   |
|
  |
Netscape Communicator 4.0 Instructions | Outlook 97 Instructions |  |
|
 |
Eudora Pro 3.0 Instructions | Outlook 98 Instructions | |
|
|
Eudora Pro 4.0 Instructions | View
mail in your master mailbox without downloading through the use of telnet. |
Important Things To Know (summary):
If you signed up for a FrontPage account, we initially installed FrontPage extensions for your site. If you decide that you no longer wish to use FrontPage, and you make this decision after the first 30 days from when you setup your account, you will be charged a $30 fee to have them removed. Likewise, if you initially signed up for an account without FrontPage, and you later decide that you want to use FrontPage, you will be charged a $30 fee for the installation of the extensions (unless you make the decision within the aforementioned 30-day grace period).
We have the FrontPage'97 extensions and Frontpage'98 extensions installed on our servers. Please tell us which version you want on your site. Frontpage'98 extensions are backwards compatible to Frontpage'97 designed sites.
If you choose to use
FrontPage'97, the only way to upload your web site(s) is with FrontPage; you CANNOT FTP into your "/frontpage/" Directory. You can use FTP
& TELNET to enter other areas of your site outside the FrontPage Directory Structure.
Sites with FrontPage'98 extensions can use FTP & TELNET to
upload files to the FrontPage Directory Structure but pages using FrontPage Web Bots must
be loaded with FrontPage.
The DocumentRoot (the directory visible to web browsers) on older frontpage installations
is named,
"/mnt/web/guide/yourdomain/frontpage" . On newer installations it is
named, "/mnt/web/guide/yourdomain/wwwfp". This is where your web content
goes, this is where Frontpage will publish to.
Every time you create a "New Web" on our server, we will have to restart your web deamon. We have now updated our Web Configuration to automatically reboot every 15 minutes if you have "Created A New Web". This means that you publish the web and the server creates the directory for it. Shut down your FrontPage Explorer for at least 15 minutes while you go get a cup of coffee. Come back and restart the FrontPage Explorer, republish your web and you are all set. This is for new sub-webs only; changes to your root web should be apparent immediately after publishing.
FrontPage is a good product, however its transfer protocol is temperamental and does not react well to heavy traffic. Therefore it is a good idea to have each of your directories created as their own sub-web, and then "publish" it to your site. Try to keep each individual web down to 1 or 2 megabytes. Larger webs will tend to "timeout" when publishing.
If you have the "Web Publishing Wizard" on your computer, you will need to uninstall it using your control panel's Add/Remove Programs feature. This Wizard is for sites that do not have the FrontPage Server Extensions installed.
If you want your
visitors to download ".exe" files from your site, there is a small amount of
work involved. First, you must place the .exe files in a subdirectory of your root
or sub-web. They cannot be in the root directory of a web or the frontpage web bots
will not work. Second, you need to create a file named .htaccess in the subdirectory
containing the .exe's . The only contents of the file will be:
AddType application/octet-stream exe EXE
This can also be done in your /docs directory if you wish to keep the files out of your
frontpage directories.
Last thing to remember is "You Must Be Online To Publish You Web".
(Sorry, all you fine non-virtual
customers - FrontPage will only work
with fully qualified domain names. Gives you incentive to upgrade, huh?!?)
That should be about it! Because it is a new method of administering your site, there will probably be kinks; we will do everything we can to help you along, though. Good Luck!
OK, your page at "http://yourdomain.com/index.html" needs that cool odometer graphic. Insert this code into the HTML code of your page:
<img src="http://yourdomain.com/cgi-bin/nph-count2?width=5&link=http://yourdomain.com/index.html">
Please Note: If you are a
FrontPage 98 user with the FrontPage 98 extensions installed on your site, please see below. If you are a FrontPage 97 user, please see further below.
If you are a FrontPage user with the FrontPage 98 extensions installed on your site, you will use this path instead:
(The difference is that you are using "cgibin" instead of "cgi-bin".)
Also, FrontPage 98 users with
FrontPage 98 extensions installed on their sites may use a FrontPage WebBot Hit Counter.
Please review your FrontPage documentation and help menu, or consult the Microsoft FrontPage site
for details (FrontPage 97 users, please see below).
Hmm, what about my page at http://yourdomain.com/somewhere/else.html? Follow this example instead:
<img src="http://yourdomain.com/cgi-bin/nph-count2?width=5&link=http://yourdomain.com/somewhere/else.html">
FrontPage 97 WebBot Hit Counters will not operate on our UNIX operating systems. You may use a third party script if you wish but we will not be able to provide technical support for it. To use ours, follow these steps:
2. Open the page with the FP editor, place the cursor where you want the counter.
3. =>Insert => HTML Markup => (insert the counter script) => OK => save file, Done.
You can set the counter by editing the
file named "count_file" in your DocumentRoot directory. This is the directory to
which you upload your web pages. In most cases, this will be called www or wwwfp.
Download this file via FTP (in
ASCII mode) and use a simple text editor (such as notepad) to change the number shown at
the end of the line that contains the name of the page that the counter you wish to set is
on. Save the file and ftp it back up (also in ASCII mode).
Done.
Please Note: If you are a
FrontPage user with the FrontPage extensions installed on your site, please see below.
You cannot ftp files to your frontpage
directory if you have Frontpage'97 extensions installed, you must use frontpage to edit
files in the frontpage directory structure. Start your frontpage and in the
"open" dialog box, type your domain name and extension. Enter your user id and
password and you are now viewing your frontpage site as it exists on our server. Right
click on count-file and choose "open with". Then choose "text
editor:notepad.exe". Edit the count at the end of the line that corresponds to the
page you wish to count and click on "save" under the file menu. Click the close
box (x) to close notepad then and close your frontpage explorer. When you view the page
with the counter on it in your browser, you will see that the count is what you set plus
one.
Imagemap URL: http://YOURDOMAIN.COM/yourmap.map (NCSA Format)
Imagemaps allow the user to click on predefined sections of a graphic picture on your page and have the server respond as if they clicked on a text hyperlink. A complete tutorial is available including a sample imagemap and helpful tools. You are encouraged to review the entire tutorial.
Yes, you can password protect specific directories within your website.
Please Note: If you are a FrontPage user with the FrontPage extensions installed on your site, please see below.
You can begin assigning unique ids and passwords by following the procedures for .htaccess. As such, visitors will be prompted for id and password to gain access to any web page within such a directory. This does NOT affect FTP access.
HTAccess is a NCSA compatible (our server is) way to use password-protection on HTML documents and server directories. The interface prompts the user through the browser for a password, if HTAccess is attached to the directory tree containing the HTML page requested. Check our .htaccess tutorial.
We recommend reviewing your FrontPage documentation and help menu, or consult the Microsoft FrontPage site for further details.
After you figure out where to put your HTML, Server Side Include commands, and CGI files, the next thing you need to learn is how to enable them so they can be used by the WWW server.
File protections also are referred to as file permissions. The file permissions tell the server who has access to your file and whether the file is a simple text file or an executable program. There are three main types of files: directories, text files, and executable files. Because you typically use Perl as your scripting language, your executable CGI programs will be both text and executable files. Directory files are special text files that are executable by the server. These files contain special directives to the server describing to the server where a group of files is located.
Each of these file types has three sets of permissions. The permissions are Read, Write and Execute. The Read permission allows the file to be opened for reading, but it cannot be modified. The Write permission allows the file to be modified but not opened for reading. The Execute permission is used both to allow program execution and director listings. If anyone, including yourself, is going to be able to get a listing or move to a directory, the Execute permission on the directory file must be set. The Execute permission also must be set for any program you want the server to run for you. Regardless of the file extension or the contents of a file, if the Execute permission is not set, the server will not try to run or execute the file when the file is called.
This is probably one of the most common reasons for CGI programs not working the first time. If you are using an interpretive language like Perl, you never run a compile and link command, so the system doesn’t automatically change the file permissions to Execute. If you write a perfectly good Perl program and then try and run it from the command line, you might get an error message like permission denied. If you test out your CGI program from your Web browser, however, you are likely to get an error –an Internet file error with a status code of 403. This error code seems kind of ominous the first time you see it, and it really doesn’t help you very much in figuring out what the problem is.
Remember that there are three types of file permissions: Read, Write, and Execute. Each of these file permissions is applied at three separate access levels. These access levels define who can see your files based on their user name and group name.
When you create a file, it gets created with your user name and your group name as the owner and group name of the file, respectively. The file’s Read, Write, and Execute permissions are set for the owner, the group, and other (sometimes referred to as world). This is very important because your Web page is likely to be accessed by anybody in the world. Usually, your Web server will run as user nobody. This means that when your CGI program is executed or your Web page is opened for reading a process with a group name different than the group name you belong to, someone else will be accessing your files. You must set your file-access permissions to allow your Web server access to your files. This usually means setting the Read and Execute privileges for the world or other group.
In order for your Web page to be opened by anyone on the Net, it must be readable by anyone in the world. In order for your CGI program to be run by anyone on the Net, it must be executable by your Internet server. Therefore, you must set the permissions so that the server can read or execute your files, which usually means making your CGI programs world executable. You set your file permissions by using a command, via telnet, called chmod (change file mode). The chmod command accepts two parameters. The first parameter is the permission mask. The second parameter is the file for which you want to change permissions. Only the owner of a file can change the file’s permissions mask. These permissions can also be set using an ftp program called WS_FTP. While viewing your site with WS_FTP, select the file or directory you wish to set permissions on and right-click on it while holding down the shift key. Select chmod (UNIX) from the pop-up menu.
The permissions mask is a three-digit number: each digit of the number defines the permission for a different user of the file. The first digit defines the permissions for the owner. The second digit defines the permissions for the group. The third digit defines the permissions for everyone else, usually referred to as the world or other, as in other groups. Each digit works the same for each group of users: the owner, group, and world. What you set for one digit has no effect on the other two digits. Each digit is made up of the three Read, Write and Execute permissions. The Read permission value is 4, the Write permission value is 2, and the Execute permission is 1. You add these three numbers together to get the permissions for a file. If you want a file to only be readable and not writeable or executable, set its permission to 4. This works the same for Write and Execute.
Executable only files have a permission of 1. If you want a file to have Read and Write permissions, add the Read and Write values together (4+2) and you get 6, the permissions setting for Read and Write. If you want the file to be Read, Write and Execute, use the value 7, derived from adding the three permissions (4+2+1). Do this for each of the three permission groups and you get a valid Chmod mask.
Suppose that you want your file to have Read, Write, and Execute permissions (4+2+1) for yourself; Read and Execute (4+1) for your group; and Execute (1) only for everyone else. You would set The file permissions to 751, using this command:
chmod 751 [filename]
Tip: If you want the world to be able to use files in a directory, but only if they know exactly what files they want, you can set the directory permission to Execute only. This means that intruders cannot do wild-card directory listings to see what type of files you have in a directory. But if someone knows what type of file she wants, she still can access that file by requesting it with a fully qualified name (no wild cards allowed).
Telnet is a communication protocol used to issue commands on a remote host. It is built into Windows95, Windows98 and WindowsNT. All accounts created after 11-20-98 have telnet initially disabled. We will enable telnet on these accounts upon customer request. You may change the master password of your account via telnet. If you wish to change your password but do not wish to use telnet, please use our Secure Web Form to notify us.
If you use an Apple MacIntosh or other non-Windows computer, telnet client software is available at:
http://www.tucows.com/UnitedStates.html
Pick a server in your region and then click on the operating system that you use. Choose Telnet from the Network Tools and download whichever program apeals to you.
You can call up telnet with Win95, 98 or NT by
following these steps:
* Click on the "Start" button
* Click on "Run"
* Type "telnet" in the box
* Click on "OK"
* (The telnet window appears)
* Click on "Connect"
* Click on "Remote System"
* Where it says Host Name, type in "yourdomain.com" or use your IP address
* Click on "OK"
* You will receive a "login:" prompt (type your userid)
* You will be prompted for your password (the characters will not be printed to the
screen)
* You should receive a prompt like the following:
www#:/mnt/web/guide/yourdomainname#
* You are now connected via a Unix telnet session and can run any standard Unix command
To view a directory's contents, type: dir
To change directories, type: cd directoryname
To change back to the previous directory, type: cd ..
To delete a file, type: rm filename
To delete a directory and all of its contents, type: rm -rf directoryname
(Unix does not have undelete and the rm command is irreversible)
To create a new directory, type: mkdir newdirectoryname
To edit a file, type: pico filename
(a list of editor commands will be at the bottom of the screen)
To rename a file (or directory), type: mv oldfilename newfilename
To move a file from one directory to another, type: mv
old/directory/path/file.name new/dir/path/file.name
To copy a file to another directory, type: cp old/dir/file new/dir/file
To copy a file with a new name (e.g. to backup a file before editing), type:
cp file file.old
To change your master password, type: passwd
To finish telnet, type: exit
( if you will be idle more than 30 minutes, please use the
exit command as open logins increase the CPU load and take
up bandwidth unnecessarily. We appreciate your cooperation
in helping us to provide the best service possible : )
(Unix can be a powerful and versatile operating system but, at first,
it will seem cryptic and complicated.We recommend getting a book
or taking a course on its use. We like "Unix for Dummies" )
Autoresponders send automatic reply messages when others send email messages to particular addresses. The autoresponders are controlled by means of the .mreply.rc file.
Note for Non-Virtual Domain accounts: The .mreply.rc file is available only for Full-Virtual accounts.
All Full-Virtual accounts have a default .mreply.rc file in their directory structure. This default file will send an autoresponse message to any mail sent to info@yourdomainname.ext. The contents of that default autoresponse message will be:
Yo <name of the person sending the mail to you> this is coming from your .mreply.rc file in your home directory. it is an auto-responder and its really cool, Jim
For example, if your domain name is xyz.com, and someone named John Doe sent a message to info@xyz.com, then John Doe would receive this autoresponse message:
Yo John this is coming from your .mreply.rc file in your home directory. it is an auto-responder and its really cool, Jim
Of course, you will want to make your own autoresponse email addresses.You can enter your custom messages to the info files located in the packets directory in your root directory. The corresponding text files to email addresses are as follows:
info@xyz.com info.txt
sales@xyz.com info2.txt
webmaster@xyz.com info3.txt
support@xyz.com info4.txt
billing@xyz.com info5.txt
You may do so by editing the .mreply.rc file; however, we suggest using a far easier method, the Chapman's .mreply.rc Generator.
If you click on the above hyperlink, you will come to a web page with a form. This is the Chapman's .mreply.rc Generator. We suggest that you print out this page, as well as the associated FAQ page, and then fill in the form.
While filling in the form, we recommend that you skip the boxes dealing with lists and fill in the boxes dealing with auto-responders.
Note: While you may fill in the part of the generator that involves lists, E-Brewer does not support the list-serve functions of mreply. If you encounter any problems related to the lists, you will be on your own in fixing them.
Note 2: E-Brewer.Com does not allow mailing lists of greater than 10 people, due to the load that larger lists can put on our servers. Accommodating large mailing lists would adversely affect the service we could give to others.
An "ErrorDocument" is the message that you see when you try to go to a web page that does not exist. The default ErrorDocument message looks like this:
File Not Found
The requested URL /xxxxxx.html was not found on this server.
(where xxxxxx.html is the name of the incorrect web page that you tried to visit).
The above ErrorDocument is not very pretty, and you may wish to make one of your own. This is how you do it:
Note: FrontPage users, please see below.
First, make a web page, and give it a name you can remember, such as badurl.html.
Second, check the directory structure of your site, to see if you have a file in your root directory (e.g., if your site is named xyz.com, then the name of the root directory would be xyz) with the name .htaccess. If you do not have such a file there, you will need to create the file with a simple text editor (such as MS Notepad for Win95 users or Simple Text for Mac users). If the file already exists, you will need to edit it with a simple text editor. You will need to add the following line to the .htaccess file:
ErrorDocument 404 /badurl.html
Third, upload the .htaccess file to your root directory, using an FTP program.
It's that simple! <Please note that directories containing .htaccess files cannot be accessed with https:// >
Note: FrontPage98 users, please see further below.
First, using FrontPage Editor, make a web page, and give it a name you can remember, such as badurl.html.
Second, check the directory structure of your site, to see if you have a file in your root directory (e.g., if your site is named xyz.com, then the name of the root directory would be xyz) with the name .htaccess. This will require the use of an FTP program. If you do not have an FTP program, or if you are unfamiliar with how to use one, please check the following links on our site:
For links to free FTP programs that you may download, please click here.
For a tutorial on the use of an FTP program, please click here.
If you do not have a .htaccess file in your root directory, you will need to create the file with a simple text editor (such as MS Notepad for Win95 users or Simple Text for Mac users). If the file already exists, you will need to edit it with a simple text editor. You will need to add the following line to the .htaccess file:
ErrorDocument 404 /badurl.html
Third, upload the .htaccess file to your root directory, using the FTP program.
It's that simple!
First, using FrontPage Editor, make a web page, and give it a name you can remember, such as badurl.html.
Second, contact Tech Support, requesting that we edit our root configuration file, to place the ErrorDocument line in it. If you add the ErrorDocument directive to the .htaccess file in your root directory, you will disable SSL for your entire site. Please tell us if you have given the ErrorDocument a name other than badurl.html.
It's that simple!
