Re: [EMAIL PROTECTED] httpd.conf for oracle app 10g

2007-05-22 Thread Josh Wyatt
Red al tubor wrote: Hello Guys, I am new here, i am facing a problem in our Oracle Application Server 10g ... i configured httpd.conf in a recommended way from oracle... The Problem is that when more than 500 session are opened the Server fails down and the cpu is running full 100% httpd

Re: [EMAIL PROTECTED] Apache Examples Extreme Web Servers

2007-03-13 Thread Josh . Wyatt
On Tue, 13 Mar 2007, linux guru wrote: Does anybody host about 2000-2500 virtual sites in single server? Which version of Apache do you prefer 2.0 or 2.2 for hosting thousands of websites? Do you have examples or some experiment about the httpd.conf for this kind of servers? Have you ever

Re: [EMAIL PROTECTED] Reverse SSL proxy with NULL cipher on backend?

2006-09-18 Thread Josh Wyatt
is enabled on on oapache. Sounds complicated, and I'm sure R. Goldberg had a hand in this. But stage 3 requires SSL. Thanks, Josh On 18/09/06, Josh Wyatt [EMAIL PROTECTED] wrote: Joshua Slive wrote: On 9/16/06, Josh Wyatt [EMAIL PROTECTED] wrote: I'd like to use NULL authentication

[EMAIL PROTECTED] Different direction - WAS: Reverse SSL proxy with NULL cipher on backend?

2006-09-18 Thread Josh Wyatt
is the format for NULL certificate files and key files? How do I generate them? Thanks, josh Josh Wyatt wrote: Spil Oss wrote: Hi Josh, When you say https is hard-coded as the beginning of all URLs you mean that that is done in all pages that the webserver generates? In that case you might

Re: [EMAIL PROTECTED] Reverse SSL proxy with NULL cipher on backend?

2006-09-17 Thread Josh Wyatt
Joshua Slive wrote: On 9/16/06, Josh Wyatt [EMAIL PROTECTED] wrote: I'd like to use NULL authentication, ciphers, etc to reduce the proxyapache - oapache SSL overhead. How can I configure oapache and proxyapache to use NULL for authentication, ciphers, etc? I don't know the answer

[EMAIL PROTECTED] Reverse SSL proxy with NULL cipher on backend?

2006-09-16 Thread Josh Wyatt
I have a situation in which I must run an old, insecure Apache (1.3.19, don't ask...). The application that runs with this webserver requires SSL from the client. Let's call this oapache. To help secure this situation, I have built a 2.0.59 with openssl configuration on this same host.