Re: [users@httpd] Httpd vhosts and ProxyPass/ProxyPassReverse and AJP - am I on crack?

You might need to change the names that the tomcat servers think of them selves as being. ie. call one server http://a.FOO.com and the other http://b.FOO.com Proxy pass reverse matches the first-hit right argument, again

[users@httpd] Inline Login with mod_auth_form 405 error

I'm trying to get couchpotato set up in a reverse proxy with apache 2.4.3 using mod_auth_form for authentication. The proxy is working fine, but the authentication is not working as expected. When I browse to my password protected url I get a 401 status which I am over riding according to the

Re: [users@httpd] rotatelogs creates logs as root

From: MegaBrutal >I've encountered a system which is configured to use the rotatelogs >application to rotate logs. For some reason, it creates subsequent log files >with root owner, while the log files should be owned by the Apache user >account. >Why is it, and what can I do to solve this pro

Re: [users@httpd] rotatelogs creates logs as root

On Tue, Nov 27, 2012 at 10:05 AM, MegaBrutal wrote: > Hello, > > I've encountered a system which is configured to use the rotatelogs > application to rotate logs. For some reason, it creates subsequent log files > with root owner, while the log files should be owned by the Apache user > account. >

Re: [users@httpd] rotatelogs creates logs as root

On Tue, Nov 27, 2012 at 10:05 AM, MegaBrutal wrote: > Hello, > > I've encountered a system which is configured to use the rotatelogs > application to rotate logs. For some reason, it creates subsequent log files > with root owner, while the log files should be owned by the Apache user > account. >

[users@httpd] rotatelogs creates logs as root

Hello, I've encountered a system which is configured to use the rotatelogs application to rotate logs. For some reason, it creates subsequent log files with root owner, while the log files should be owned by the Apache user account. Why is it, and what can I do to solve this problem? Apache runs

Re: [users@httpd] Interesting Problem

- Original Message - From: "Igor Cicimov" To: "users" Sent: Monday, November 26, 2012 5:49:19 PM Subject: Re: [users@httpd] Interesting Problem On Tue, Nov 27, 2012 at 6:03 AM, Chris Arnold < carn...@electrichendrix.com > wrote: #This will be the default vhost because the

[users@httpd] virtualhost and redirection

Hi, in order to provide an access to custoemrs to our developent server, i decided to use NO-IP service and to bind my dynamic IP address to a DDNS. so now customer can connect to server using e.g. http://myserver.no-ip.org:8080 i change the port to avoid conflict issues and on my wireless ro

Re: [users@httpd] Interesting Problem

More specific this: Default one is the one that is defined first in the list of vhosts no matter if its name starts with 000 or not. On 27/11/2012 8:18 PM, "Igor Cicimov" wrote: > > > On 27/11/2012 7:16 PM, "Igor Galić" wrote: > > > > > > > > - Original Message - > > > > > > > > > # Cat

Re: [users@httpd] Interesting Problem

On 27/11/2012 7:16 PM, "Igor Galić" wrote: > > > > - Original Message - > > > > > > # Catch all VHost, traffic that is NOT going to domain.net > > > > ServerName localhost_name.domain.net > > > > RewriteEngine On > > RewriteCond %{HTTP_HOST} ^192\.168\.123\.3$ > > RewriteRule .* https://d

Re: [users@httpd] connectiontimout question

- Original Message - > On Tue, Nov 27, 2012 at 2:59 AM, Smith, Mitchell < > mitchell.sm...@cwc.com > wrote: > > > connectiontimeout > > I would expect the timeout value for the particular worker or the > ProxyTimeout to be increased and not the connectiontimeout. The > connectiontimeou

Re: [users@httpd] Interesting Problem

- Original Message - > > > # Catch all VHost, traffic that is NOT going to domain.net > > ServerName localhost_name.domain.net > > RewriteEngine On > RewriteCond %{HTTP_HOST} ^192\.168\.123\.3$ > RewriteRule .* https://domain.net [R,L] > # or do what ever you like with this > > -->Pr