- At
http://www.apache.org
- Apache performance tuning -
http://www.apache.org/docs/misc/perf-tuning.html
- log rotation/log-rotation/rotating logs
From: "Andrew" grof@home.com
Newsgroups: comp.infosystems.www.servers.unix,comp.infosystems.www.servers.misc
Subject: Re: Log file rotation - what a nightmare with Apache :-(
Date: Thu, 06 May 1999 12:35:23 GMT
Try this, it works:
mv /path/to/old/log/file /path/to/new/log/file
touch /path/to/new/log/file
kill -HUP [pid of apache]
the last line can be done using the file that contains the pid of apache...
eg.
kill -HUP `cat /path/to/httpd.pid`
or if you wanted, you could grep through your ps aux (althogh the previous
is better)
kill -HUP `ps aux | grep httpd | tail -1`
Oh the power! :)
You can get past without HUP'ing Apache... It is needed.
It shouldn't hurt you. If you have problems restarting than it is likely
your .conf files are screwed and you would have had problems down the line
anyways. Fix 'em now while you can.
Good luck with it!
Andrew
#! /usr/local/bin/bash
HTTPD_LOGS_DIR=/opt/httpd/logs # path to httpd log dir
HTTPD_PID=/opt/httpd/logs/httpd.pid # path to httpd pid
YYMMDD=`/usr/bin/date +%Y%m%d`
cd $HTTPD_LOGS_DIR
mv -f access_log access_log.$YYMMDD
mv -f error_log error_log.$YYMMDD
kill -USR1 `cat $HTTPD_PID`
sleep 15
gzip -9f access_log.$YYMMDD error_log.$YYMMDD
- To prevent caching from the browser, try using both the Expires and the Pragma command simultaneously.
Hi Lachlan,
I now have a foolproof (?) way to prevent caching. Adding a
random parameter to the URL will always fetch it again eg
http..../icsd/tmp/myFile.wrl?$RANDOM is the same as:
http..../icsd/tmp/myFile.wrl - except the former is not cached
if $RANDOM is a random string eg a number generated by perl:
srand(); $RANDOM=substr(rand(99),0,2); #2 digit random no.
Alan Hewat, ILL Grenoble, FRANCE tel (33) 4.76.20.72.13
ftp://ftp.ill.fr/pub/dif fax (33) 4.76.20.76.48 http://www.ill.fr/dif/
From: "Joshua Slive" <slive+news@finance.commerce.ubc.ca>
Newsgroups: comp.infosystems.www.servers.unix
Subject: Re: Apache Redirect/ReWrite for redirecting old->new domains?
Date: 7 Jul 1999 17:21:47 GMT
Organization: The University of British Columbia
Frampton Steve R <3srf@qlink.queensu.ca> wrote:
> Hello:
> I'm having some difficulty getting Apache to redirect page requests with
> an informative message. My place of employment is moving from their old
> domain name to a new one. We now have both of these domain names active,
> both of which point to the same server. Although we will be phasing out
> the old address very soon, people continue accessing the pages at the old
> address, hence the reason for the redirect.
> Putting something like <META HTTP-EQUIV="refresh"
> "CONTENT=05;URL=http://newdomain.com/newpage"> in all our pages is not
> an optimal solution because (a) there are hundreds of pages that would
> need to be updated, (b) this solution doesn't display an informative
> message before the redirect, and (c) Apache provides a better solution.
I think that your syntax is a little off. Check the Apache docs for
the relevant directives. What I would do is something like
RewriteEngine On
RewriteRule ^/~test/(.*) /redirector.shtml/$1
Then configure /redirector.shtml as an SSI parsed document looking
something like
<HTML>
<HEAD><TITLE>This page has moved</TITLE>
<META HTTP-EQUIV="refresh"
CONTENT="05;URL=http://newdomain.com/~test/<!--#echo var="PATH_INFO" -->">
<BODY>
<H1>This page has moved</H1>
<P>The new location is <A HREF="http://newdomain.com/~test/<!--#echo
var="PATH_INFO" -->">here</A>. You will be redirected automatically
in 5 seconds. Please update your bookmarks.
</BODY>
</HTML>
This is completely untested, and probably has errors, but it should
get you started. You could also use a cgi script instead of the SSI
mark@knm.org wrote:
> I have several virtual hosts which I would like to share the same
> directory, but instead of pointing to index.html I would like to have
> different index pages for each.
>
What you want is this
<VirtualHost www.ford.com>
...
DocumentRoot /usr/local/webpages
DirectoryIndex ford_index.html
</VirtualHost>
<VirtualHost www.chevy.com>
...
DocumentRoot /usr/local/webpages
DirectoryIndex chevy_index.html
</VirtualHost>
Note this chenges the index.html default to the supplied one in all the
subdirectories in your document tree as well, but only for the virtual
host in question.
The Pilgrim
Subject: Re: Firewall positioning
CERT paper on firewall security issues and best practices.
http://www.cert.org/security-improvement/modules/m08.html
Contrary to some answers you may have received:
a) never leave a web server where it is not protected (in front of a firewall)
b) do not allow inbound connections through a firewall to your internal
network (unless you are a security expert and know the risks or you have it
checked by a security expert)
c) so that leaves you with 1 primary option: get a single firewall and use 3
interfaces: 1 to your internal network, 1 to a DMZ (a semi-secure area that is
designed for serving inbound requests) and 1 to the Internet.
..more complex answers are available but require in-depth knowledge of the
situation and the expertise to evaluate the options...
- Re: Thwarting mass .htaccess crack attempts, how?
My personal preference (may not be available or may be different
of various unix-flavors, YMMV) is:
route add -blackhole 62.2.252.230 127.0.0.1
And *any* packets from the offendee are simply dropped by the kernel.
Or, if it is in your purview, similarly at your firewall or router.