On Sat, 2009-01-24 at 16:53 +0100, Norman Khine wrote:
> Hi,
>
>
> Eric Covener wrote:
> > On Sat, Jan 24, 2009 at 10:20 AM, Norman Khine wrote:
> >> [Sat Jan 24 18:46:57 2009] [error] [client 86.219.32.244] client denied by
> >> server configuration: /usr/htdocs
> >
> > You don't have a that
On Sat, Jan 24, 2009 at 6:31 PM, André Warnier wrote:
> Sorry to butt in, but is it not just the RewriteCond that is badly written ?
> So should
> RewriteCond $1 !=robots.txt
> not be
> RewriteCond %1 !=robots.txt
No, The logic in the RewriteCond referring back to the RewriteRule
backreference
Norman Khine wrote:
[...]
Hi.
Sorry to butt in, but is it not just the RewriteCond that is badly written ?
From the Apache documentation :
(http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html)
# RewriteRule backreferences: These are backreferences of the form $N
(0 <= N <= 9), which provide
Hi,
Eric Covener wrote:
On Sat, Jan 24, 2009 at 10:20 AM, Norman Khine wrote:
[Sat Jan 24 18:46:57 2009] [error] [client 86.219.32.244] client denied by
server configuration: /usr/htdocs
You don't have a that allows you to serve
static files out of the filesystem. If this is a new Documen
On Sat, Jan 24, 2009 at 10:20 AM, Norman Khine wrote:
> [Sat Jan 24 18:46:57 2009] [error] [client 86.219.32.244] client denied by
> server configuration: /usr/htdocs
You don't have a that allows you to serve
static files out of the filesystem. If this is a new DocumentRoot you
added, copy the
Bob Ionescu wrote:
2009/1/23 Norman Khine :
RewriteEngine On
#DenyHosts Rules
RewriteMap hosts-deny txt:/home/user/txt/hosts.deny
RewriteCond ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR]
RewriteCond ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND [OR]
Rew
2009/1/23 Norman Khine :
> RewriteEngine On
> #DenyHosts Rules
> RewriteMap hosts-deny txt:/home/user/txt/hosts.deny
> RewriteCond ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR]
> RewriteCond ${hosts-deny:%{REMOTE_ADDR}|NOT-FOUND} !=NOT-FOUND [OR]
> RewriteCond ${h
Hi,
This is what I have:
ServerName domain.com
ServerAlias www.domain.com
RewriteEngine On
#DenyHosts Rules
RewriteMap hosts-deny txt:/home/user/txt/hosts.deny
RewriteCond ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR]
RewriteCond ${hosts-deny:%{REMOTE
On Thu, Jan 22, 2009 at 3:46 PM, Norman Khine wrote:
> Hi, sorry, but this did not work.
> As now when I type the http://domain.com/robots.txt the page returned
> is from within my cms application and not from the default
The condition you added didn't stop the request from being proxied?
Did you
Hi, sorry, but this did not work.
As now when I type the http://domain.com/robots.txt the page returned
is from within my cms application and not from the default
I am using the python framework itools (http://www.hforge.org) and
this has in its URI a semi-column i.e. http://www.hforge.org/;view
2009/1/22 Norman Khine :
> Is there a way I can put a robots.txt file to reside outside of the
> rewrite, so that if a the bots look for http://domain.com/robots.txt
> the rewrite does not push it to the
> localhost:12080/companies/robots.txt
Just exclude the specific path:
RewriteCond $1 !=robot
Hello,
I have the following http.conf entry:
ServerName domain.com
ServerAlias www.domain.com
RewriteEngine On
#DenyHosts Rules
RewriteMaphosts-deny txt:/home/user/txt/hosts.deny
RewriteCond ${hosts-deny:%{REMOTE_HOST}|NOT-FOUND} !=NOT-FOUND [OR]
Rewri
12 matches
Mail list logo
