Re: [users@httpd] ssl offloading behind a proxy

2016-12-16 Thread Miguel González
The bottom line is that I need to get different logs for each domain for webalizer. How can I do that tagging so is understood by those stats applications? On 12/16/16 6:05 PM, Jim Jagielski wrote: > Why not put all accesses in a single log, with an extra tag on > whether or not it was via

Re: [users@httpd] Trubble with rewrite rules

2016-12-16 Thread Thomas Schweikle
On 16.12.2016 16:46, Eric Covener wrote: > On Fri, Dec 16, 2016 at 10:26 AM, Thomas Schweikle > wrote: >>RewriteRule ^/xyz/(.*) "/abc/$1" [R,L] > > > When this rule was first -- If it's in htaccess, the ^/ will not > match. Your other rule accounts for this by making

Re: [users@httpd] ssl offloading behind a proxy

2016-12-16 Thread Jim Jagielski
Why not put all accesses in a single log, with an extra tag on whether or not it was via SSL/HTTPS? > On Dec 16, 2016, at 11:41 AM, Miguel González > wrote: > > Nobody? > > On 12/11/16 7:45 PM, Miguel González wrote: >> Dear all, >> >> I am using Apache to

Re: [users@httpd] ssl offloading behind a proxy

2016-12-16 Thread Miguel González
Nobody? On 12/11/16 7:45 PM, Miguel González wrote: > Dear all, > > I am using Apache to offload SSL to non-ssl Apache running behind a > Varnish server. I do that with proxypass. Everything running WHM in a > Centos 6.8 server. > > I do that because Varnish doesn´t manage HTTPs requests so

Re: [users@httpd] Trubble with rewrite rules

2016-12-16 Thread Eric Covener
On Fri, Dec 16, 2016 at 10:26 AM, Thomas Schweikle wrote: >RewriteRule ^/xyz/(.*) "/abc/$1" [R,L] When this rule was first -- If it's in htaccess, the ^/ will not match. Your other rule accounts for this by making the leading slash optional. -- Eric Covener

[users@httpd] Trubble with rewrite rules

2016-12-16 Thread Thomas Schweikle
Hi! I am redirecting all connections to https: RewriteEngine On RewriteCond %{HTTPS} !=on RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L] That is working so far. Now an other thing to do I've moved some content to an other place and I want users accessing the old place to be

Re: [users@httpd] Issue During Cname Switch

2016-12-16 Thread Eric Covener
On Fri, Dec 16, 2016 at 6:50 AM, Ajay B wrote: > Once we restart the apache it passed the request to new server. > > Please help us in fixing this issue. The manual says: DNS resolution happens when the socket to the origin domain is created for the first time.

Re: [users@httpd] Issue During Cname Switch

2016-12-16 Thread Ajay B
Hi Yehuda We changed only the DNS configuration not the HTTPD. Thanks Ajay On Fri, Dec 16, 2016 at 7:41 PM, Yehuda Katz wrote: > Your question doesn't say whether you are changing the HTTPD configuration > or just changing the DNS. > > Any time you change the HTTPD

Re: [users@httpd] Issue During Cname Switch

2016-12-16 Thread Yehuda Katz
Your question doesn't say whether you are changing the HTTPD configuration or just changing the DNS. Any time you change the HTTPD configuration you need to restart the service. There is no way around that. If that isn't the problem, try describing the steps you take when you make a change. - Y

[users@httpd] Issue During Cname Switch

2016-12-16 Thread Ajay B
Hi All We are using Apache HTTPD server and pointing to our server using cname. Whenever we point the cname to different server the apache is not able to recognize it till we restart the httpd service. Once we restart the apache it passed the request to new server. Please help us in fixing