[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] .htaccess error document help?

we too have had one crisis after another with the htaccess on the raq 4

all of our mod_rewrite rules and add handlers did not work on the 4...

i called up cobalt and they said it was a tightening of security ...

i say not so fast....

everything worked on the raq3...
escilations agreed to modify my server to allow the various htaccess function 

we would be interested in learning more about your err pgm...

here is the "Fix":


The File that I modified on your system was in this location:

	/etc/httpd/conf/access.conf

attached to this email is the original(access.conf.master) and the
modified
one(access.conf)

To restore the prior configuration, ftp the access.conf.master file to
the
server as admin into admin's home directory, the directory you are in
as soon
as you log in.

Then telnet to the machine, log in as admin then at the command prompt
type

	su
and enter admin's password when asked for a passoword.

Then type
	cp access.conf.master /etc/httpd/conf/access.conf
this will restore the prior configuration.

Any further questions please call the support line or use the online
form to
submit questions through email.  Please do not respond to this address,
as it
will not produce rapid response.

Regards,
Jason Williams

--------------------------------------------------------------------------------

##
## access.conf -- Apache HTTP server configuration file
##

# access.conf: Global access configuration
# Online docs at http://www.apache.org/

# This file defines server settings which affect which types of
services
# are allowed, and in what circumstances.

# Each directory to which Apache has access, can be configured with
respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).

# Originally by Rob McCool

# First, we configure the "default" to be a very restrictive set of
# permissions.

<Directory />
Options None
AllowOverride AuthConfig Indexes Limit
AuthFailDelay 2000000
</Directory>

# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.

# deal with symlinks in image directory
<Directory /usr/admserv/html/.cobalt/images/>
Options +SymLinksIfOwnerMatch
</Directory>

# This should be changed to whatever you set DocumentRoot to.

<Directory /home/sites/>

# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".

# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.

Options Indexes FollowSymLinks Includes MultiViews

# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options",
"FileInfo",
# "AuthConfig", and "Limit"

AllowOverride All

# ignore .ht*
<Files ".ht*">
deny from all
</Files>

# Controls who can get stuff from this server.

order allow,deny
allow from all

AuthFailDelay 2000000

# Frontpage subwebs use a nice mix of pam and Basic authentication
AuthPAM_FallThrough on

</Directory>

# be more restrictive within a site
<Directory /home/sites/*/>
Options -FollowSymLinks +SymLinksIfOwnerMatch
</Directory>

# @@ServerRoot@@/cgi-bin should be changed to whatever your
ScriptAliased
# CGI directory exists, if you have that configured.

#<Directory /home/httpd/cgi-bin>
#AllowOverride None
#Options ExecCGI
#</Directory>

# Allow server status reports, with the URL of
http://servername/server-status
# Change the ".your_domain.com" to match your domain to enable.

#<Location /server-status>
#SetHandler server-status

#order deny,allow
#deny from all
#allow from .your_domain.com
#</Location>

# There have been reports of people trying to abuse an old bug from
pre-1.1
# days.  This bug involved a CGI script distributed as a part of
Apache.
# By uncommenting these lines you can redirect these attacks to a
logging
# script on phf.apache.org.  Or, you can record them yourself, using
the script
# support/phf_abuse_log.cgi.

#<Location /cgi-bin/phf*>
#deny from all
#ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
#</Location>

# You may place any other directories or locations you wish to have
# access information for after this one.


<Directory /home/sites/home>
AllowOverride All
Options All
</Directory>


--------------------------------------------------------------------------------

##
## access.conf -- Apache HTTP server configuration file
##

# access.conf: Global access configuration
# Online docs at http://www.apache.org/

# This file defines server settings which affect which types of
services
# are allowed, and in what circumstances.

# Each directory to which Apache has access, can be configured with
respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).

# Originally by Rob McCool

# First, we configure the "default" to be a very restrictive set of
# permissions.

<Directory />
Options None
AllowOverride None
AuthFailDelay 2000000
</Directory>

# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.

# deal with symlinks in image directory
<Directory /usr/admserv/html/.cobalt/images/>
Options +SymLinksIfOwnerMatch
</Directory>

# This should be changed to whatever you set DocumentRoot to.

<Directory /home/sites/>

# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".

# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.

Options Indexes FollowSymLinks Includes MultiViews

# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options",
"FileInfo",
# "AuthConfig", and "Limit"

AllowOverride None

# ignore .ht*
<Files ".ht*">
deny from all
</Files>

# Controls who can get stuff from this server.

order allow,deny
allow from all

AuthFailDelay 2000000

# Frontpage subwebs use a nice mix of pam and Basic authentication
AuthPAM_FallThrough on

</Directory>

# be more restrictive within a site
<Directory /home/sites/*/>
Options -FollowSymLinks +SymLinksIfOwnerMatch
</Directory>

# @@ServerRoot@@/cgi-bin should be changed to whatever your
ScriptAliased
# CGI directory exists, if you have that configured.

#<Directory /home/httpd/cgi-bin>
#AllowOverride None
#Options ExecCGI
#</Directory>

# Allow server status reports, with the URL of
http://servername/server-status
# Change the ".your_domain.com" to match your domain to enable.

#<Location /server-status>
#SetHandler server-status

#order deny,allow
#deny from all
#allow from .your_domain.com
#</Location>

# There have been reports of people trying to abuse an old bug from
pre-1.1
# days.  This bug involved a CGI script distributed as a part of
Apache.
# By uncommenting these lines you can redirect these attacks to a
logging
# script on phf.apache.org.  Or, you can record them yourself, using
the script
# support/phf_abuse_log.cgi.

#<Location /cgi-bin/phf*>
#deny from all
#ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi
#</Location>

# You may place any other directories or locations you wish to have
# access information for after this one.




From: "S. Berg" <sberg@xxxxxxx>
Reply-To: cobalt-users@xxxxxxxxxxxxxxx
To: <cobalt-users@xxxxxxxxxxxxxxx>
Subject: [cobalt-users] .htaccess error document help?
Date: Tue, 20 Feb 2001 21:15:08 -0800

Hi,

I have been running raq2 and raq3's for some time now and have just began
migrating to raq4's. The problem I am having is I always set up each site
with a custom .htaccess file in the web directory to redirect 404's to a
script which loads a predefined page by the customer. This has worked fine
on the older RaQ's but now when I install it on a RaQ4 I get an internal
server error. I am guessing that something is turned off or different in
Apache now. Here is what the file looks like:

ErrorDocument 401 /cgi-bin/errorbot.cgi?401
ErrorDocument 403 /cgi-bin/errorbot.cgi?403
ErrorDocument 404 /cgi-bin/errorbot.cgi?404
ErrorDocument 500 /cgi-bin/errorbot.cgi?500

It calls a script to feed the page but apparently the RaQ4 is configured to
not allow it.

Does anyone know how to turn this back on or the best way to have custom
error pages for each site instead of the generic cobalt?

Thanks for your time

Shon


_______________________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To Subscribe or Unsubscribe, please go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com