Web publishing details
Hit logs
Web hit logs are not currently processed. They are however,
split up by user. You can find the log information for each
user in /usr/local/www/logs/users/username/*.
Virtual host hits are stored with the logs for the user
that owns the domain.
The hit logs take disk space. The disk space used by your
hit logs will count towards the disk usage of your account.
To control the disk space for your web logs, visit the
Account Management Wizard
section of the main web page.
Error logs
Web server error logs can be found in the directory
/usr/local/www/logs. Each virtual server has its
own error log. For a server named www.ackbar.com,
the error log would be host.ackbar.com-error_log.
Error logs for hits through www.idiom.com are stored
in the file error_log.
When you are debugging CGI programs, it is helpful to see the
error log information as it is written. Use the shell command
tail -f logfile watch the log get written.
Server-side includes
Server-side includes are supported, but includes are limited
to files -- not programs. The syntax for a server side include
is <!--#include file="filename" -->.
Server-side include files must have a file extension of
.shtml or they must have the execute bit on in their
unix permissions.
.htaccess files
Using .htaccess files, you can control many features of your
private web space. For example, you can password-protect pages.
See http://www.apache.org/docs/core.html#allowoverride for a
discussion of what you can do.
The overrides that are allowed are:
- AuthConfig
- FileInfo
- Indexes
- Limit
The .htaccess file and any password file that it
references must be readable to the user httpd.
Password protecting your web pages
Here's a recipe for password protecting your web pages. This
recipe is for the user bob, so please substitute in your
own login as appropriate. You should cut and paste the entire
section after replacing bob. Please note that the prompt
may change during the course of entering these commands, you
should simply ignore it and continue to cut and paste.
<![CDATA[
cd
cd public_html
mkdir private
chgrp users private
chmod 705 private
cd private
cat <<EOF > .htaccess
AuthUserFile /home/bob/.webaccess
AuthName SecurityTest
AuthType Basic
require valid-user
EOF
chmod 704 .htaccess
cd
htpasswd -c .webaccess user1
htpasswd .webaccess user2
chgrp users .webaccess
chmod 704 .webaccess
]]>
Once you've followed the above recipe, put the files you wish to
keep private in public_html/private.
Icons and GIFs
There are number of icons and GIFs available for use in your
documents installed on idiom.
To see what's available, look at:
http://www.idiom.com/icons/.
Server status
Cookies
By default, Idiom's web server will give "cookies" to each
visitor. Cookies are tokens that web servers give to web
browsers and then the web browsers give them back to the web
servers.
All you can do with a cookie is tell how many people came to
your web site and what each of them did. You cannot tell who they
are or what other web sites they've visited.
Some people don't like cookies. If you don't want cookies on
your web pages, create a file in your web directory called:
.htaccess. In that file, put the following line:
CookieTracking off
Server configuration
Idiom uses Apache version 1.3b3.
User web pages are served with the following configuration
options:
In addition, there are
handlers
for the following file extensions:
- .shtml: server side includes
- .asis: send a document as-is
- .cgi: CGI scripts/programs
- .nph: No-parse-header CGI scripts/programs
- .mhtml: Meta-HTML scripts
- .phtmp: PHP/FI scripts
- .var: negotiated content
