Re: [users@httpd] Send header apache to java (jboss) through ajp

2017-03-30 Thread Nacho Fernandez
Hi Eric, java app expect this content: --BEGIN CERTIFICATE--x--END CERTIFICATE-- or xxx ..in both cases this is public certificate client. If you save this content to 'file.crt' you can view it. The problem is that the content receive in jboss side is: *X-Client-Cert:

Re: [users@httpd] Send header apache to java (jboss) through ajp

2017-03-30 Thread Eric Covener
On Thu, Mar 30, 2017 at 6:30 PM, Nacho Fernandez wrote: > [truncated] X-Client-Cert: ——BEGIN > CERTIFICATE——XX—END CERTIFICATE—— > > The Header name is sent!! with content. But i need receive this one so that > application be able to read public certificate client: > > [tru

[users@httpd] Send header apache to java (jboss) through ajp

2017-03-30 Thread Nacho Fernandez
Hi everyone, i need send header content “*X-Client-Cert*” from Apache Web Server to java application deploy in Jboss, through AJP protocol. With directive below, in Apache Virtual Host, i check Header reach Jboss but application not found because

Re: [users@httpd] mod_auth_cas issue ....

2017-03-30 Thread FHDATA
hello, anybody knows if mod_auth_cas has any mailing list so I can post this issue there? ones I found on the net are all "dead" (bounced when contacted) thank you, F- On Mon, 27 Mar 2017, FHDATA wrote: Apache/3.2.15 mod_auth_cas 1.1 on rhel6 we have a VirtualHost defined as: Ser

[users@httpd] DH parameter selection on httpd 2.2

2017-03-30 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'm running httpd 2.2.31 on Amazon Linux, and the docs for SSLCertificateFile say: " Beginning with version 2.2.30, mod_ssl makes use of standardized DH parameters with prime lengths of 2048, 3072, 4096, 6144 and 8192 bits (from RFC 3526), and

[users@httpd] Issue with proxy to IIS

2017-03-30 Thread Joe Muller
We are running Apache 2.4.18 with mod_proxy and recently moved a backend site from a Weblogic server to an IIS server, and now we are facing intermittent issues when users connect. Users tend to receive the error: Proxy Error The proxy server received an invalid response from an upstream serve

RE: [users@httpd] Apache Builds on Linux

2017-03-30 Thread Houser, Rick
Perhaps this is a mis-defined problem where you've just assumed you need to relocate the binaries? Do you just need the ability to have multiple simultaneous installs of Apache or the ability for users to use storage paths outside your control/knowledge? If you set the prefix to a version-spec

Re: [users@httpd] RE: Enabling Forward secrecy on SSL

2017-03-30 Thread Daniel
2017-03-30 14:07 GMT+02:00 Abernathy, Don : > Most common way we did this was in the Virtual host directive for the SSL > side of the site, was to declare what is and is not allowed. > > Plenty of docs on this out there but here is ours: > > > This is IBM HTTP Server not Apache HTTPD! > > > SSL

Re: [users@httpd] Apache Builds on Linux

2017-03-30 Thread Eric Covener
On Thu, Mar 30, 2017 at 1:28 PM, Abernathy, Don wrote: > Yes, I did.. in both files and cases, and yet when you start it, it refuses > to start. You'll need to deep-dive on the specifics and resolve them one at a time. -- Eric Covener cove...@gmail.com

RE: [users@httpd] Apache Builds on Linux

2017-03-30 Thread Abernathy, Don
Yes, I did.. in both files and cases, and yet when you start it, it refuses to start. @Rick, I get the build, and that works for me, I can just build the package with the prefix being what you noted (Yes topo on the space when I started the e-mail) but like noted, I would like to make it portab

[users@httpd] RE: Apache Builds on Linux

2017-03-30 Thread Houser, Rick
Don't move stuff around once you have things built, or you will break things, just like with most other non-trivial software. The --prefix is where you intend for it to live once all is done, so if you want it to live in /opt/WebSite/Apache1, just put that in the prefix. If you want to tempora

Re: [users@httpd] Apache Builds on Linux

2017-03-30 Thread Eric Covener
On Thu, Mar 30, 2017 at 7:50 AM, Abernathy, Don wrote: > what I did was use a prefix like /opt/BaseBuild and that works as expected > but now when I copy that Apache to a new home, say /opt/WebSite/Apache1 and > try to start it, it keeps pointing to /opt/BaseBuild. Do you change all the referen

[users@httpd] RE: Enabling Forward secrecy on SSL

2017-03-30 Thread Abernathy, Don
Most common way we did this was in the Virtual host directive for the SSL side of the site, was to declare what is and is not allowed. Plenty of docs on this out there but here is ours: SSLEnable SSLProtocolDisable SSLv2 SSLv3 SSLCipherSpec ALL NONE SSLCipherSpec TLSv12 TLS_ECDHE_RSA_WITH_AES_12

[users@httpd] Apache Builds on Linux

2017-03-30 Thread Abernathy, Don
Preface this with new to this subject but: We have always used an apache instance that was a bundled solution, such at IBM version, and now want to build our own. The build process is well documented, that is not the issue, the deployment is the issue. what I did was use a prefix like /opt/Base

Re: [users@httpd] using tee to feed logs to executable

2017-03-30 Thread Eric Covener
So no eof In your piped loggers should be expected. On Wed, Mar 29, 2017, 11:20 PM Milind Vaidya wrote: > it does not restart apache it just copytruncates erro_log file. > > On Wed, Mar 29, 2017 at 6:19 PM, Eric Covener wrote: > > On Wed, Mar 29, 2017 at 9:16 PM, Milind Vaidya wrote: > > But w

Re: [users@httpd] What is preferred PHP interface?

2017-03-30 Thread Mitchell Krog Photography
+1 php-fpm From: Lester Caine Reply: users@httpd.apache.org Date: 30 March 2017 at 11:14:57 AM To: users@httpd.apache.org Subject: Re: [users@httpd] What is preferred PHP interface? On 30/03/17 02:00, John Iliffe wrote: > Surprised that the PHP docs don't seem to have anything equiva

Re: [users@httpd] What is preferred PHP interface?

2017-03-30 Thread Lester Caine
On 30/03/17 02:00, John Iliffe wrote: > Surprised that the PHP docs don't seem to have anything equivalent to that > Wiki. The equivalent page for PHP is perhaps https://secure.php.net/manual/en/install.php, but with the growing number of alternatives to Apache it's difficult to keep everything u