Re: [users@httpd] Change https to port 8000 instead of 443

2012-09-20 Thread techienote . com
Hi,

What is there in error logs?

Sent on my BlackBerry® from Vodafone

-Original Message-
From: Kheng_Ee 
Date: Thu, 20 Sep 2012 22:16:24 
To: users@httpd.apache.org
Reply-To: users@httpd.apache.org
Subject: Re: [users@httpd] Change https to port 8000 instead of 443
Correction :  I change  57.4.223.96:8443 to 192.168.1.1:8000 in virtualhost. 
still not working.



 From: Kheng_Ee 
To: "users@httpd.apache.org"  
Sent: Friday, 21 September 2012 3:13 PM
Subject: [users@httpd] Change https to port 8000 instead of 443
 

I am using Apache Version 2.4.3 and it is working using port 80 (http) and 443 
(https).

I would like to use port 8000 instead of 443 for https

In http.conf file, it has 

Listen 192.168.1.1:8000 https


In the extra/http-ssl.conf.  it has

.
.




It is supposed to be this simple but it is not accepting anything from the 
browser.

Even if I change the , nothing works.
ServerName ksim:8443
Protocol https
.

What is missing ?

There is no issue with the connectivity as I can telnet to port 8000.


Re: [users@httpd] Change https to port 8000 instead of 443

2012-09-20 Thread Kheng_Ee
Correction :  I change  57.4.223.96:8443 to 192.168.1.1:8000 in virtualhost. 
still not working.



 From: Kheng_Ee 
To: "users@httpd.apache.org"  
Sent: Friday, 21 September 2012 3:13 PM
Subject: [users@httpd] Change https to port 8000 instead of 443
 

I am using Apache Version 2.4.3 and it is working using port 80 (http) and 443 
(https).

I would like to use port 8000 instead of 443 for https

In http.conf file, it has 

Listen 192.168.1.1:8000 https


In the extra/http-ssl.conf.  it has

.
.




It is supposed to be this simple but it is not accepting anything from the 
browser.

Even if I change the , nothing works.
ServerName ksim:8443
Protocol https
.

What is missing ?

There is no issue with the connectivity as I can telnet to port 8000.

[users@httpd] Change https to port 8000 instead of 443

2012-09-20 Thread Kheng_Ee
I am using Apache Version 2.4.3 and it is working using port 80 (http) and 443 
(https).

I would like to use port 8000 instead of 443 for https

In http.conf file, it has 

Listen 192.168.1.1:8000 https


In the extra/http-ssl.conf.  it has

.
.




It is supposed to be this simple but it is not accepting anything from the 
browser.

Even if I change the , nothing works.
ServerName ksim:8443
Protocol https
.

What is missing ?

There is no issue with the connectivity as I can telnet to port 8000.

RE: [users@httpd] Apache Proxy configuration question

2012-09-20 Thread Jeremy T

Hi Vivek,
Thanks. Do you mean a trailing slash after /demo/ or do you mean /demo / 
https://internal2:82
For eg...
 Proxypass /demo/ https://internal2:82 ProxyPassReverse /demo/ 
https://internal2:82  ProxyPass / https://internal1:81 ProxyPassReverse / 
https://internal1:81 


or 
 Proxypass /demo / https://internal2:82 ProxyPassReverse /demo / 
https://internal2:82  ProxyPass / https://internal1:81 ProxyPassReverse / 
https://internal1:81  

ThanksJeremy
Date: Wed, 19 Sep 2012 17:40:55 +0530
From: vivek1namb...@gmail.com
To: users@httpd.apache.org
Subject: Re: [users@httpd] Apache Proxy configuration question

Hi Jeremy,
If you add a / infront of the SSL URL,then does it work?
Thanks

On Wed, Sep 19, 2012 at 11:43 AM, Jeremy T  wrote:





Hi All,
I had a question about Apache with SSL.Basically came across this issue when 
configuring a reverse proxy with Apache.
Do you know if there is some limitation on the number of ProxyPass and 
ProxPassReverse entries that you can do when it comes to an SSL virtual host?

Consider the following scenario:1. I have a website called http://public1 and 
have a public SSL cert for that site.2. I have two internal servers with 
different urls containing self signed SSL certs for both of them.
3. Internal urls are https://internal1:81 and https://internal2:824. I would 
like to have https://public1 proxy to https://internal1:81 and 
https://public1/demo proxy to https://internal2:82

 
Configuration:
 Proxypass /demo https://internal2:82 ProxyPassReverse /demo 
https://internal2:82 
 ProxyPass / https://internal1:81
 ProxyPassReverse / https://internal1:81



The problem:It seems that the /demo entries do not work (the first two 
entries). However these rules work for non SSL virtual hosts. The problem is 
when I work with SSL virtual hosts.

ANY help / tips or limitations with the above would be helpful.

Thank you
Jeremy

  

  

Re: [users@httpd] httpd 2.2 ReverseProxy not working on 302 redirect location header

2012-09-20 Thread Mario A. del Riego
El 19/09/12 12:06, Tom Evans escribió:
> On Wed, Sep 19, 2012 at 3:46 PM, Mario A. del Riego
>  wrote:
>> Supid,
>>
>> I have the same behavior, it's a bug well documented at [1].
>>
>> If you know the redirection, you can do it in the front-end.
>> In my particular case, i fixed it with mod_security. I have wrote a
>> little in my blog [0] (in spanish) about this.
>>
>>
>> [0] http://blog.makam.org/2012/09/01/bug-en-mod_proxy/
>> [1] https://issues.apache.org/bugzilla/show_bug.cgi?id=51489
>>
> 
> I don't believe this is a bug. In the configuration he says
> 
>   ProxyPassReverse / http://fooremote.com/
> 


oops, i misread the problem.
It has nothing to do with my situation.

Sorry.

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] rotatelogs: does it create directories?

2012-09-20 Thread Tom Evans
On Thu, Sep 20, 2012 at 2:10 PM, Mark Montague  wrote:
> On September 20, 2012 7:01 , "Esmond Pitt"  wrote:
>>
>> Sorry, can't wait till the end of the month to experiment with this. It
>> occurred to me that I would like to organize my log files by year and month
>> in directories. Does rotatelogs create intermediate directories if they
>> don't exist?
>
>
> Cronolog will do this, see  http://cronolog.org/
>
> I like cronolog because:
>

+1, we use cronolog for all our logging needs. It's small, easy to
use, and never (touch wood) goes wrong.

Cheers

Tom

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] rotatelogs: does it create directories?

2012-09-20 Thread Mark Montague

On September 20, 2012 7:01 , "Esmond Pitt"  wrote:
Sorry, can't wait till the end of the month to experiment with this. 
It occurred to me that I would like to organize my log files by year 
and month in directories. Does rotatelogs create intermediate 
directories if they don't exist?


Cronolog will do this, see  http://cronolog.org/

I like cronolog because:

- You never have to signal httpd to re-open log files.  New logs are 
created automatically.
- No need for cron jobs unless you want to delete old log files after 
some period of time.
- Logs are written directly to their long-term filename; files do not 
get renamed.
- cronolog maintains symbolic links to the latest logs so that they can 
be accessed without needing to deal with the directory structure or dates.
- cronolog runs as a non-root user separate from the user that httpd 
runs as, which helps keep logs secure while minimizing potential 
vulnerabilities.

- More flexibility in log naming than rotatelogs.

I recommend downloading "cronolog 1.7 beta with the jumbo patch 
applied", which you can get from 
http://cronolog.org/patches/index.htmlThis has worked well for me in 
production for years now, and it has significantly more features than 
cronolog 1.6.2.


cronolog works well with SELinux if you add the following local policy:

policy_module(cronolog, 1.0)

require {
type httpd_log_t;
type httpd_t;
class lnk_file { create unlink };
class dir { remove_name };
}

allow httpd_t httpd_log_t:lnk_file { create unlink };
allow httpd_t httpd_log_t:dir { remove_name };


When I have the time -- hopefully later this year -- I'd like to write a 
complete SELinux policy module for cronolog so that it doesn't get all 
of the extra access that httpd has, as it does now.


--
  Mark Montague
  m...@catseye.org


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] rotatelogs: does it create directories?

2012-09-20 Thread Eric Covener
On Thu, Sep 20, 2012 at 7:01 AM, Esmond Pitt  wrote:
> Sorry, can't wait till the end of the month to experiment with this. It
> occurred to me that I would like to organize my log files by year and month
> in directories. Does rotatelogs create intermediate directories if they
> don't exist?
>

No.

(you can run rotatelogs on the command line without httpd)

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



Re: [users@httpd] hive hbase integration

2012-09-20 Thread Jeff Trawick
On Thu, Sep 20, 2012 at 7:42 AM, subhashini.514
 wrote:
> Hi,
>
> We want to insert data into Hbase cluster.

Please leave users@httpd.apache.org off of further messages in this thread.

-- 
Born in Roswell... married an alien...
http://emptyhammock.com/

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



[users@httpd] rotatelogs: does it create directories?

2012-09-20 Thread Esmond Pitt
Sorry, can't wait till the end of the month to experiment with this. It
occurred to me that I would like to organize my log files by year and month
in directories. Does rotatelogs create intermediate directories if they
don't exist?
 
EJP


Re: [users@httpd] Rewrites not working in 'server config'

2012-09-20 Thread Igor Cicimov
On Sep 19, 2012 8:46 PM, "David Hubbard" 
wrote:
>
> Is there a trick to getting rewrites working in the
> base config file?

Put

RewriteOptions inherit

in the virtual hosts.

I'm trying to block a bad bot
> by user agent server-wide, I tested it in one site and
> have the relevant rewrites working fine in .htaccess,
> but when moving them to the global config, it does
> not work.
>
> I tried wrapping in a directory clause for the parent
> directory that holds all the websites, that didn't
> help.  The rewrite directives (engine on, condition
> and rule) only seem to work in htaccess or in the
> virtual host directives.
>
> Thanks!
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>