Re: [users@httpd] REQUEST_URI multiple wildcard pattern

[Arunkumar Janarthanan]

Thanks Lee, for your reply.

I could use !^/(files|admin|user|product|go), however this would allow all
wildcard pattern for the URI string like "user/login" ? or
"products/newarrival" ?

Is why I tried with (.*) but the wildcard string still not getting picked up
by the rule.

On Sat, Apr 30, 2011 at 2:22 AM, Lee  wrote:

>
>
> On 30/04/2011 05:46, Arunkumar Janarthanan wrote:
> > Hi,
> >
> > I have a request that the site contains specific URI pattern should
> > go to another URL while the other URI patterns goes to 404 page of
> > external site.
> >
> > Here below the rule I have written, however this is not working for
> > wildcard match of the URI pattern.
> >
> > RewriteCond %{REQUEST_URI}
> > !^/(files(.*)|admin(.*)|user(.*)|product(.*)|go(.*))$ RewriteRule .*
> > http://www.abc.com/page-not-found [R=301,NC,L]
>
> RewriteCond %{REQUEST_URI} !^/(files|admin|user|product|go)
>
> Round brackets are good for grouping OR clauses (produce|admin),
> and good for storing back-references (.*). But you are not using
> back-references, so you can drop a lot of those brackets. Also,
> you can simply your use of the gobble-everything operator (.*)
>  by putting it at the end - although why would you need it?
>
> You simply need to match a few phrases at the beginning of the
> string.
>
> So:
>
> ! If REQUEST_URI does not match
> ^ from the start
> / oblique
> (files|admin|user|product|go) any of these phrases
>
> HTH
> Lee
>
>

Re: [users@httpd] REQUEST_URI multiple wildcard pattern

[Lee Goddard]

Hi Arunkumar

You wrote,

I could use !^/(files|admin|user|product|go), however this would allow 
all wildcard pattern for the URI string like "user/login" ? or 
"products/newarrival" ?


This is not true. Nothing beginning with the words files, or admin, or 
user, or product, or go, would match.


You do not need to terminate the pattern with a wildcard -- you have a 
match at the beginning.


What is it exactly that you are trying to achieve?

Lee


On 30/04/2011 12:44, Arunkumar Janarthanan wrote:

Thanks Lee, for your reply.

I could use !^/(files|admin|user|product|go), however this would allow 
all wildcard pattern for the URI string like "user/login" ? or 
"products/newarrival" ?


Is why I tried with (.*) but the wildcard string still not getting 
picked up by the rule.


On Sat, Apr 30, 2011 at 2:22 AM, Lee > wrote:




On 30/04/2011 05:46, Arunkumar Janarthanan wrote:
> Hi,

>

> I have a request that the site contains specific URI pattern
should

> go to another URL while the other URI patterns goes to 404
page of

> external site.

>

> Here below the rule I have written, however this is not
working for

> wildcard match of the URI pattern.

>

> RewriteCond %{REQUEST_URI}

> !^/(files(.*)|admin(.*)|user(.*)|product(.*)|go(.*))$
RewriteRule .*

> http://www.abc.com/page-not-found [R=301,NC,L]

RewriteCond %{REQUEST_URI} !^/(files|admin|user|product|go)

Round brackets are good for grouping OR clauses (produce|admin),
and good for storing back-references (.*). But you are not using
back-references, so you can drop a lot of those brackets. Also,
you can simply your use of the gobble-everything operator (.*)
 by putting it at the end - although why would you need it?

You simply need to match a few phrases at the beginning of the
string.

So:

! If REQUEST_URI does not match
^ from the start
/ oblique
(files|admin|user|product|go) any of these phrases

HTH
Lee

RE: [users@httpd] Apache is too slow with SSL

[Tushar Chavan]

Hi Ishita,
 
I am also same facing problem. Can you please let me know if you find any 
solution.
 
Best Regards,
Tushar.
 
> Date: Tue, 12 Apr 2011 22:09:39 -0400
> From: ishim...@gmail.com
> To: users@httpd.apache.org
> CC: traw...@gmail.com
> Subject: Re: [users@httpd] Apache is too slow with SSL
> 
> Hi Jeff,
> 
> SSL session cache is utilized maximum as out of 3 requests 29850
> requests was served as "session reuse" during my stress test
> 
> Thanks
> 
> On Fri, Apr 8, 2011 at 10:06 AM, Jeff Trawick  wrote:
> > On Wed, Apr 6, 2011 at 11:09 PM, Ishita Kapadiya  wrote:
> >> Hi Jeff,
> >>
> >> both ab and JMETER is using keep alive.
> >
> > keepalive and reusing SSL sessions isn't the same thing
> >
> > reusing the SSL session (avoiding the expensive part of the handshake)
> > deals with what happens when the client opens a subsequent TCP
> > connection (after sending however many keepalive requests on a prior
> > connection)
> >
> >> I am using SSL session cache
> >> in the config as -
> >> SSLSessionCache"shmcb:/path to logs/ssl_scache(512000)"
> >>
> >>> Even if so, it is worth using mod_ssl tracing to confirm that the
> >>> combination of client/server behavior results in a reasonably high
> >>> session cache utilization.
> >>
> >> Please let me know how can i trace mod_ssl to confirm session cache 
> >> utilization.
> >
> > with LogLevel debug, look for messages like
> >
> > Inter-Process Session Cache: request=GET status=XXX
> >
> > XXX will indicate whether or not the session was found in the cache
> >
> > -
> > The official User-To-User support forum of the Apache HTTP Server Project.
> > See http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> >   "   from the digest: users-digest-unsubscr...@httpd.apache.org
> > For additional commands, e-mail: users-h...@httpd.apache.org
> >
> >
> 
> -
> The official User-To-User support forum of the Apache HTTP Server Project.
> See http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> " from the digest: users-digest-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
> 
  

Re: [users@httpd] REQUEST_URI multiple wildcard pattern

[Arunkumar Janarthanan]

Hi Lee,

sorry for posting the requirement as it is, this is what the requirement
exactly.

1. http://xyz.com/esweep* - no redirection at all  (so urls like
esweepconfirm/thank-you/ do not redirect)
2. http://xyz.com/user* - no redirection at all
3. http://xyz.com/files/* - no redirection at all
4. http://xyz.com/admin* - no redirection at all
5. http://xyz.com/go - no redirection at all
6. All other - redirect to http://www.abc.com/page-not-found

Best Regards,
Arun J

On Sat, Apr 30, 2011 at 7:44 AM, Lee Goddard  wrote:

>  Hi Arunkumar
>
> You wrote,
>
>
> I could use !^/(files|admin|user|product|go), however this would allow all
> wildcard pattern for the URI string like "user/login" ? or
> "products/newarrival" ?
>
> This is not true. Nothing beginning with the words files, or admin, or
> user, or product, or go, would match.
>
> You do not need to terminate the pattern with a wildcard -- you have a
> match at the beginning.
>
> What is it exactly that you are trying to achieve?
>
> Lee
>
>
>
> On 30/04/2011 12:44, Arunkumar Janarthanan wrote:
>
> Thanks Lee, for your reply.
>
> I could use !^/(files|admin|user|product|go), however this would allow all
> wildcard pattern for the URI string like "user/login" ? or
> "products/newarrival" ?
>
> Is why I tried with (.*) but the wildcard string still not getting picked
> up by the rule.
>
> On Sat, Apr 30, 2011 at 2:22 AM, Lee  wrote:
>
>>
>>
>> On 30/04/2011 05:46, Arunkumar Janarthanan wrote:
>> > Hi,
>>
>> >
>>
>> > I have a request that the site contains specific URI pattern
>> should
>>
>> > go to another URL while the other URI patterns goes to 404
>> page of
>>
>> > external site.
>>
>> >
>>
>> > Here below the rule I have written, however this is not
>> working for
>>
>> > wildcard match of the URI pattern.
>>
>> >
>>
>> > RewriteCond %{REQUEST_URI}
>>
>> > !^/(files(.*)|admin(.*)|user(.*)|product(.*)|go(.*))$
>> RewriteRule .*
>>
>> > http://www.abc.com/page-not-found [R=301,NC,L]
>>
>>  RewriteCond %{REQUEST_URI} !^/(files|admin|user|product|go)
>>
>> Round brackets are good for grouping OR clauses (produce|admin),
>> and good for storing back-references (.*). But you are not using
>> back-references, so you can drop a lot of those brackets. Also,
>> you can simply your use of the gobble-everything operator (.*)
>>  by putting it at the end - although why would you need it?
>>
>> You simply need to match a few phrases at the beginning of the
>> string.
>>
>> So:
>>
>> ! If REQUEST_URI does not match
>> ^ from the start
>> / oblique
>> (files|admin|user|product|go) any of these phrases
>>
>> HTH
>> Lee
>>
>>
>

Re: [users@httpd] Apache is too slow with SSL

[Bostjan Skufca]

Just tried it on one of my servers, I get a ratio of 0,7% in ssl vs non-ssl
ab benchmark, without keepalive. With keepalive it gets to 1/3.

However, I noticed something else a year or so ago, never figured out the
cause.
I can't get apache to work faster than 11k req/s, no matter how many
concurrent clients I use. On the same hardware nginx goes up to 30k req/s.
(request here contains mere 14 bytes of static content, small compared to
even HTTP headers it consumes). Here's the graph:
http://blog.a2o.si/wp-content/uploads/2009/06/HelloWorld.txt.png

And the whole article (a bit dated now):
http://blog.a2o.si/2009/06/24/apache-mod_php-compared-to-nginx-php-fpm/

b.


On 30 April 2011 13:57, Tushar Chavan  wrote:

>  Hi Ishita,
>
> I am also same facing problem. Can you please let me know if you find any
> solution.
>
> Best Regards,
> Tushar.
>
> > Date: Tue, 12 Apr 2011 22:09:39 -0400
> > From: ishim...@gmail.com
> > To: users@httpd.apache.org
> > CC: traw...@gmail.com
> > Subject: Re: [users@httpd] Apache is too slow with SSL
> >
> > Hi Jeff,
> >
> > SSL session cache is utilized maximum as out of 3 requests 29850
> > requests was served as "session reuse" during my stress test
> >
> > Thanks
> >
> > On Fri, Apr 8, 2011 at 10:06 AM, Jeff Trawick  wrote:
> > > On Wed, Apr 6, 2011 at 11:09 PM, Ishita Kapadiya 
> wrote:
> > >> Hi Jeff,
> > >>
> > >> both ab and JMETER is using keep alive.
> > >
> > > keepalive and reusing SSL sessions isn't the same thing
> > >
> > > reusing the SSL session (avoiding the expensive part of the handshake)
> > > deals with what happens when the client opens a subsequent TCP
> > > connection (after sending however many keepalive requests on a prior
> > > connection)
> > >
> > >> I am using SSL session cache
> > >> in the config as -
> > >> SSLSessionCache"shmcb:/path to logs/ssl_scache(512000)"
> > >>
> > >>> Even if so, it is worth using mod_ssl tracing to confirm that the
> > >>> combination of client/server behavior results in a reasonably high
> > >>> session cache utilization.
> > >>
> > >> Please let me know how can i trace mod_ssl to confirm session cache
> utilization.
> > >
> > > with LogLevel debug, look for messages like
> > >
> > > Inter-Process Session Cache: request=GET status=XXX
> > >
> > > XXX will indicate whether or not the session was found in the cache
> > >
> > > -
> > > The official User-To-User support forum of the Apache HTTP Server
> Project.
> > > See http://httpd.apache.org/userslist.html> for more info.
> > > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> > >   "   from the digest: users-digest-unsubscr...@httpd.apache.org
> > > For additional commands, e-mail: users-h...@httpd.apache.org
> > >
> > >
> >
> > -
> > The official User-To-User support forum of the Apache HTTP Server
> Project.
> > See http://httpd.apache.org/userslist.html> for more info.
> > To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> > " from the digest: users-digest-unsubscr...@httpd.apache.org
> > For additional commands, e-mail: users-h...@httpd.apache.org
> >
>

Re: [users@httpd] REQUEST_URI multiple wildcard pattern

[Lee]

Hi Arunkumar

You have a list of URIs to NOT match for redirection, so begin the 
pattern, as you did, with !


RewriteRule !

You then have a group of top-level directory or files to be ignored, so 
you can anchor at the start of the URI:


RewriteRule !^/

Then put all your dir/file names in braces, delimited by the OR operator, I

RewriteRule !^/(this|that)

Then follow with the URI to which everything should be directed that 
does not match:


RewriteRule !^/(this|that) http://your-other-host/page-not-page.

I wasn't quite sure about your spec's use of wildcards, sometimes you 
have them after an /oblique/, sometimes without, sometimes not at all. I 
assumed that was a typo, and that every item should have a wildcard 
star. If that is not the case, please drop me a line off-list.


HTH
Lee

PS There is a note on wildcards in ! negated patterns, and why to avoid 
them:


  http://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriterule

Note
When using the NOT character to negate a pattern, you cannot include 
grouped wildcard parts in that pattern. This is because, when the 
pattern does NOT match (ie, the negation matches), there are no contents 
for the groups. Thus, if negated patterns are used, you cannot use |$N| 
in the substitution string!



On 30/04/2011 14:05, Arunkumar Janarthanan wrote:


 Hi Lee,

 sorry for posting the requirement as it is, this is what the
 requirement exactly.

 1. http://xyz.com/esweep* - no redirection at all (so urls like
 esweepconfirm/thank-you/ do not redirect) 2. http://xyz.com/user* -
 no redirection at all 3. http://xyz.com/files/* - no redirection at
 all 4. http://xyz.com/admin* - no redirection at all 5.
 http://xyz.com/go - no redirection at all 6. All other - redirect to
 http://www.abc.com/page-not-found

 Best Regards, Arun J

 On Sat, Apr 30, 2011 at 7:44 AM, Lee Goddard mailto:lee...@gmail.com>> wrote:

 Hi Arunkumar

 You wrote,


 I could use !^/(files|admin|user|product|go), however this would
 allow all wildcard pattern for the URI string like "user/login" ? or
 "products/newarrival" ?

 This is not true. Nothing beginning with the words files, or admin,
 or user, or product, or go, would match.

 You do not need to terminate the pattern with a wildcard -- you have
 a match at the beginning.

 What is it exactly that you are trying to achieve?

 Lee



 On 30/04/2011 12:44, Arunkumar Janarthanan wrote:
> Thanks Lee, for your reply.
>
> I could use !^/(files|admin|user|product|go), however this would
> allow all wildcard pattern for the URI string like "user/login" ?
> or "products/newarrival" ?
>
> Is why I tried with (.*) but the wildcard string still not getting
> picked up by the rule.
>
> On Sat, Apr 30, 2011 at 2:22 AM, Lee  > wrote:
>
>
>
> On 30/04/2011 05:46, Arunkumar Janarthanan wrote:
>> Hi,
>
>
>
>>
>
>
>
>> I have a request that the site contains specific
> URI pattern
>
> should
>
>
>
>> go to another URL while the other URI patterns
> goes to 404
>
> page of
>
>
>
>> external site.
>
>
>
>>
>
>
>
>> Here below the rule I have written, however this
> is not
>
> working for
>
>
>
>> wildcard match of the URI pattern.
>
>
>
>>
>
>
>
>> RewriteCond %{REQUEST_URI}
>
>
>
>>
> !^/(files(.*)|admin(.*)|user(.*)|product(.*)|go(.*))$
>
> RewriteRule .*
>
>
>
>> http://www.abc.com/page-not-found
> [R=301,NC,L]
>
> RewriteCond %{REQUEST_URI} !^/(files|admin|user|product|go)
>
> Round brackets are good for grouping OR clauses (produce|admin),
> and good for storing back-references (.*). But you are not using
> back-references, so you can drop a lot of those brackets. Also, you
> can simply your use of the gobble-everything operator (.*) by
> putting it at the end - although why would you need it?
>
> You simply need to match a few phrases at the beginning of the
> string.
>
> So:
>
> ! If REQUEST_URI does not match ^ from the start / oblique
> (files|admin|user|product|go) any of these phrases
>
> HTH Lee
>
>

Re: [users@httpd] REQUEST_URI multiple wildcard pattern

[Arunkumar Janarthanan]

Thank you very much Lee, appreciate your assistance with this issue. However
with the below rule the URI pattern with actual string even is not working.

Like I said when I try with wget www.xyz.com/files that goes to
www.abc.com/page-not-found.

RewriteRule !^/(files|admin|user|product|go)$
http://www.abc.com/page-not-found [R=301,NC,L]

Thanks once again for helping me on this.

On Sat, Apr 30, 2011 at 12:00 PM, Lee  wrote:

>  Hi Arunkumar
>
> You have a list of URIs to NOT match for redirection, so begin the pattern,
> as you did, with !
>
> RewriteRule !
>
> You then have a group of top-level directory or files to be ignored, so you
> can anchor at the start of the URI:
>
> RewriteRule !^/
>
> Then put all your dir/file names in braces, delimited by the OR operator, I
>
> RewriteRule !^/(this|that)
>
> Then follow with the URI to which everything should be directed that does
> not match:
>
> RewriteRule !^/(this|that) http://your-other-host/page-not-page.
>
> I wasn't quite sure about your spec's use of wildcards, sometimes you have
> them after an /oblique/, sometimes without, sometimes not at all. I assumed
> that was a typo, and that every item should have a wildcard star. If that is
> not the case, please drop me a line off-list.
>
> HTH
> Lee
>
> PS There is a note on wildcards in ! negated patterns, and why to avoid
> them:
>
>
> http://httpd.apache.org/docs/current/mod/mod_rewrite.html#rewriterule
>
> Note
> When using the NOT character to negate a pattern, you cannot include
> grouped wildcard parts in that pattern. This is because, when the pattern
> does NOT match (ie, the negation matches), there are no contents for the
> groups. Thus, if negated patterns are used, you cannot use |$N| in the
> substitution string!
>
>
>
> On 30/04/2011 14:05, Arunkumar Janarthanan wrote:
> >
> > Hi Lee,
> >
> > sorry for posting the requirement as it is, this is what the
> > requirement exactly.
> >
> > 1. http://xyz.com/esweep* - no redirection at all (so urls like
> > esweepconfirm/thank-you/ do not redirect) 2. http://xyz.com/user* -
> > no redirection at all 3. http://xyz.com/files/* - no redirection at
> > all 4. http://xyz.com/admin* - no redirection at all 5.
> > http://xyz.com/go - no redirection at all 6. All other - redirect to
> > http://www.abc.com/page-not-found
> >
> > Best Regards, Arun J
> >
> > On Sat, Apr 30, 2011 at 7:44 AM, Lee Goddard  >  > wrote:
> >
> > Hi Arunkumar
> >
> > You wrote,
> >
> >
> > I could use !^/(files|admin|user|product|go), however this would
> > allow all wildcard pattern for the URI string like "user/login" ? or
> > "products/newarrival" ?
> >
> > This is not true. Nothing beginning with the words files, or admin,
> > or user, or product, or go, would match.
> >
> > You do not need to terminate the pattern with a wildcard -- you have
> > a match at the beginning.
> >
> > What is it exactly that you are trying to achieve?
> >
> > Lee
> >
> >
> >
> > On 30/04/2011 12:44, Arunkumar Janarthanan wrote:
> >> Thanks Lee, for your reply.
> >>
> >> I could use !^/(files|admin|user|product|go), however this would
> >> allow all wildcard pattern for the URI string like "user/login" ?
> >> or "products/newarrival" ?
> >>
> >> Is why I tried with (.*) but the wildcard string still not getting
> >> picked up by the rule.
> >>
> >> On Sat, Apr 30, 2011 at 2:22 AM, Lee  >>  > wrote:
> >>
> >>
> >>
> >> On 30/04/2011 05:46, Arunkumar Janarthanan wrote:
> >>> Hi,
> >>
> >>
> >>
> >>>
> >>
> >>
> >>
> >>> I have a request that the site contains specific
> >> URI pattern
> >>
> >> should
> >>
> >>
> >>
> >>> go to another URL while the other URI patterns
> >> goes to 404
> >>
> >> page of
> >>
> >>
> >>
> >>> external site.
> >>
> >>
> >>
> >>>
> >>
> >>
> >>
> >>> Here below the rule I have written, however this
> >> is not
> >>
> >> working for
> >>
> >>
> >>
> >>> wildcard match of the URI pattern.
> >>
> >>
> >>
> >>>
> >>
> >>
> >>
> >>> RewriteCond %{REQUEST_URI}
> >>
> >>
> >>
> >>>
> >> !^/(files(.*)|admin(.*)|user(.*)|product(.*)|go(.*))$
> >>
> >> RewriteRule .*
> >>
> >>
> >>
> >>> http://www.abc.com/page-not-found
> >> [R=301,NC,L]
> >>
> >> RewriteCond %{REQUEST_URI} !^/(files|admin|user|product|go)
> >>
> >> Round brackets are good for grouping OR clauses (produce|admin),
> >> and good for storing back-references (.*). But you are not using
> >> back-references, so you can drop a lot of those brackets. Also, you
> >> can simply your use of the gobble-everything operator (.*) by
> >> putting it at the end - although why would you need it?
> >>
> >> You simply need to match a few phrases at the beginning of the
> >> string.
> >>
> >> So:
> >>
> >> ! If REQUEST_URI does not match ^ from the start / oblique
> >> (files|admin|user|product|go) any of these phrases
> >>
> >> HTH Lee
> >>
> >>
> >
>
>
>

Re: [users@httpd] MaxClients stuck at 10 bug

[Marion McCoskey]

I get this when I do a httpd -v
<<
Server version: Apache/2.2.3
Server built:   Jan 31 2011 17:49:25
>>

I have attached my httpd.conf

Thanks for your help.  I appreciate it.  If there's anything I can do,
please let me know.

Marion


httpd.conf
Description: Binary data

-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
   "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] REQUEST_URI multiple wildcard pattern

[Eric Covener]

On Sat, Apr 30, 2011 at 12:41 PM, Arunkumar Janarthanan
 wrote:
> Thank you very much Lee, appreciate your assistance with this issue. However
> with the below rule the URI pattern with actual string even is not working.
>
> Like I said when I try with wget www.xyz.com/files that goes to
> www.abc.com/page-not-found.
>
> RewriteRule !^/(files|admin|user|product|go)$
> http://www.abc.com/page-not-found [R=301,NC,L]

If this is in htaccess or , drop the leading slash.  The
"current" prefix, ending in a slash, is removed before you compare in
this context.

-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
   "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

[users@httpd] MaxClients stuck at 10 bug

[Marion McCoskey]

Here is some more info that might be useful.

I got this from yum:

<<
Installed Packages
Name   : httpd
Arch   : i386
Version: 2.2.3
Release: 45.el5.centos
Size   : 3.1 M
Repo   : installed
Summary: Apache HTTP Server
>>

I also had the problem with the original installed configuration file.

I have attached a copy.

Thanks again,

Marion


httpd.bak
Description: application/trash

-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
   "   from the digest: users-digest-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] 403 error on Default Directory

[J. Stephens]

The solution to the problem was that I needed to add  a  to the 
vhost. I do not know why it would need the root directory, but as long as it is 
fixed then I do not care. Would this cause any security risks or is it fine to 
add this directory?

BTW: Thank you for your responses it has helped a bunch.
On Apr 28, 2011, at 10:30 PM, Yehuda Katz wrote:

> On Thu, Apr 28, 2011 at 1:53 PM, J. Stephens  wrote:
> error log says "[Thu Apr 28 13:50:57 2011] [error] [client 98.226.168.246] 
> client denied by server configuration: /"
> my website is at /var/www/testing600.remcycle.net/. Should it be saying that 
> directory and not the root directory?
>> On Thu, Apr 28, 2011 at 10:37 AM, J. Stephens  
>> wrote:
>> I am getting 403 errors when I add a new vhost. at testing601.remcycle.net I 
>> get 403, but at testing601.remcycle.net/index.html it works. What are the 
>> possible causes of this 403 error?
> 
> All it is telling you is the configuration that is being inherited from a 
> config for /.
> 
> The closest thing I have to Debian Squeeze is Ubuntu Lucid Lynx (10.04). It 
> has this comment in "/etc/apache2/conf.d/security":
> # Disable access to the entire file system except for the directories that
> # are explicitly allowed later.
> #
> # This currently breaks the configurations that come with some web application
> # Debian packages. It will be made the default for the release after lenny.
> #
> #
> #   AllowOverride None
> #   Order Deny,Allow
> #   Deny from all
> #
> 
> Since Squeeze is after Lenny, this might mean that a good place to start 
> looking for your problem is wherever you have your  /var/www/testing600.remcycle.net/> directive.
> 
> Do you have the mod_info handler enabled? It might be able to help find the 
> offending directive.
> (Documentation: http://httpd.apache.org/docs/2.2/mod/mod_info.html)
> 
> 
> - Yehuda

Re: [users@httpd] 403 error on Default Directory

[Yehuda Katz]

On Fri, Apr 29, 2011 at 11:00 AM, J. Stephens wrote:

> The solution to the problem was that I needed to add  a  to
> the vhost. I do not know why it would need the root directory, but as long
> as it is fixed then I do not care. Would this cause any security risks or is
> it fine to add this directory?
>

I would not recommend doing that. You should add permissions for as few
directories as possible.
If it only works when you add the root directory, then you have some other
problem and you should probably try to find out what it is.

- Yehuda