Re: [users@httpd] Fwd: Virtualhost location variable

2011-04-15 Thread Mark Montague
On April 15, 2011 18:19 , "Michele Mase'" wrote: I need to block the access on a particular location,as the example: ... Order Deny,Allow Deny from all Allow from localhost safenet1 safenet2 ... ... I need to do the same for all the virtualhosts, more than 1K... You should be able to put t

[users@httpd] Fwd: Virtualhost location variable

2011-04-15 Thread Michele Mase'
Anyone? -- Forwarded message -- From: Michele Mase' Date: Wed, Mar 30, 2011 at 10:30 AM Subject: Virtualhost location variable To: users@httpd.apache.org I've the following situation: I need to block the access on a particular location,as the example: ... Order Deny,Allow Deny

Re: [users@httpd] mod_rewrite does not change URL in browser

2011-04-15 Thread Jeff Shearer
Perfect. Thanks for the fresh brain. == Jeff Shearer, CISA, CISSP -Original Message- From: "Pablo Garcia Melga" [mal...@gmail.com] Date: 04/15/2011 01:22 PM To: users@httpd.apache.org Subject: Re: [users@httpd] mod_rewrite does not change URL in browser Jeff, from yo

RE: [users@httpd] mod_jk type log for mod_proxy_balancer?

2011-04-15 Thread Anthony J. Biacco
Turned out to be easier than I expected. In case anybody is interested, I did this: LogFormat "%t \"%m %U\" %>s Sz %B BR %I BS %O TMSec %D TSec %T Bal %{BALANCER_NAME}e WRt %{BALANCER_WORKER_ROUTE}e PID %{pid}P TID %{tid}P UID %{UNIQUE_ID}e VHost %v" combined-tomcat CustomLog logs/proxy-tomcat.log

Re: [users@httpd] mod_rewrite does not change URL in browser

2011-04-15 Thread Pablo Garcia Melga
Jeff, from your log you seem to be requesting /oldsite, but in your rewrite rule you specify that only requests that ends with .html will be taken into consideration. a request to /oldsite/index.html should work. Regards, Pablo On Fri, Apr 15, 2011 at 2:46 PM, Jeff Shearer wrote: > Thanks Eric f

Re: [users@httpd] mod_rewrite does not change URL in browser

2011-04-15 Thread Jeff Shearer
Thanks Eric for the quick response. However, it still doesn't work. I copied you suggestion to the substitute part of the command as well as using the actual host and domain with no success. Following is the rewrite.log using your suggestion letter for letter: 192.168.9.20 - - [15/Apr/2011:1

Re: [users@httpd] mod_rewrite does not change URL in browser

2011-04-15 Thread Eric Covener
On Fri, Apr 15, 2011 at 1:02 PM, Jeff Shearer wrote: > I am trying to move a set of documents from one directory to a new directory. >  Currently users are redirected to the new directory but the old URL remains > in the browser window.  My research indicates that if I change the PT flag to > R

[users@httpd] mod_rewrite does not change URL in browser

2011-04-15 Thread Jeff Shearer
I am trying to move a set of documents from one directory to a new directory. Currently users are redirected to the new directory but the old URL remains in the browser window. My research indicates that if I change the PT flag to R I should be able to do what I want. However, when I change t

[users@httpd] Re: mod_reqtimeout not returning 408

2011-04-15 Thread Guillaume Bilodeau
A little more information on the 200 return code: It seems that mod_reqtimeout is not closing the connection after the 20 seconds, but rather truncating the request and letting it go through. So the request is actually processed, and since the URL is referring to an actual resource, a 200 code is

[users@httpd] mod_reqtimeout not returning 408

2011-04-15 Thread Guillaume Bilodeau
Hi all, In order to protect ourselves from a slowloris-type attack, we have configured the mod_reqtimeout module on our Apache 2.2.17 installation (running on Solaris, MPM compiled). The mod_reqtimeout is configured as follows: RequestReadTimeout header=10-20,MinRate=500 body=10-20,MinRate=500

Re: [users@httpd] configuration error: couldn't check access. Check your 'Require' directive

2011-04-15 Thread Admin Cyanide
You're right. httpd -M doesn't show authz_user_module. Sorry for the inconvenience and thank you for the fast reply. Bastien Semene Administrateur Réseau& Système Cyanide Studio - FRANCE Le 15/04/2011 11:27, Nick Kew a écrit : On 15 Apr 2011, at 10:16, Admin Cyanide wrote: [Fri Apr 15 10

Re: [users@httpd] configuration error: couldn't check access. Check your 'Require' directive

2011-04-15 Thread Nick Kew
On 15 Apr 2011, at 10:16, Admin Cyanide wrote: > [Fri Apr 15 10:17:37 2011] [crit] [client 62.73.7.64] configuration error: > couldn't check access. Check your 'Require' directive: / > require valid-user So you need to load mod_authz_user. > I checked the modules compiled : > # grep

[users@httpd] configuration error: couldn't check access. Check your 'Require' directive

2011-04-15 Thread Admin Cyanide
Hi list, I'm setting up a new vhost and have this error currently : [Fri Apr 15 10:17:37 2011] [crit] [client 62.73.7.64] configuration error: couldn't check access. Check your 'Require' directive: / [Fri Apr 15 10:17:37 2011] [crit] [client 62.73.7.64] configuration error: couldn't check a