Re: [users@httpd] Re: security reports page blank ???

On 03/14/2016 04:25 PM, Good guy wrote: On 14/03/2016 23:03, Richard wrote: Date: Monday, March 14, 2016 15:57:21 -0700 From: "Michael A. Peters" http://httpd.apache.org/security_report.html Currently I am getting nothing from that page, not even historic stuff. Is

[users@httpd] Re: security reports page blank ???

On 14/03/2016 23:03, Richard wrote: Date: Monday, March 14, 2016 15:57:21 -0700 From: "Michael A. Peters" http://httpd.apache.org/security_report.html Currently I am getting nothing from that page, not even historic stuff. Is this temporary or has it moved? It

[users@httpd] RE: Apache fails to start after updating openssl from 1.0.1j to 1.0.2g

I decided to upgrade the site to Apache 2.4.17. OpenSSL 1.0.2g was included and all is working well. Ron - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail:

Re: [users@httpd] security reports page blank ???

> Date: Monday, March 14, 2016 15:57:21 -0700 > From: "Michael A. Peters" > > http://httpd.apache.org/security_report.html > > Currently I am getting nothing from that page, not even historic > stuff. Is this temporary or has it moved? > It works fine for me, using

[users@httpd] security reports page blank ???

http://httpd.apache.org/security_report.html Currently I am getting nothing from that page, not even historic stuff. Is this temporary or has it moved? - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For

[users@httpd] Apache fails to start after updating openssl from 1.0.1j to 1.0.2g

Hello, I tried updating the version of OpenSSL on my Apache web server from 1.0.1j to 1.0.2g and now the web server won't start (actually I dropped back so I'm not totally freaking out). It appears to be failing before it can write to the error log. To update I simply copied openssl.exe,

[users@httpd] Ache 2.4 and LetsEncrypt

After setting up lets encrypt on my server and running it I end up with the following files: $ ls -nls total 48 8 -rw--- 1 443 443 1854 Mar 4 23:38 cert-1457159890.csr 0 -rw--- 1 443 443 0 Mar 4 23:38 cert-1457159890.pem 8 -rw--- 1 443 443 1854 Mar 5 05:06

[users@httpd] How to add data to body request

Hi! I am developing an Apache module in C and I would like to put some information into the body request (post). How could I add content in the post body request? I have seen the body_table param in request_rec, but it didn't work. Thanks!

Re: [users@httpd] Potential HTTP/2 Bug within Apache 2.4.18

Good to hear! I will update the bug. Thanks. > Am 14.03.2016 um 13:08 schrieb Russel Van Tuyl : > > Stefan, version 1.2.8 works great. Thanks for the fix and for your help. I > create a bug report with Apache yesterday. Do you want to update it or would > you like me

Re: [users@httpd] Potential HTTP/2 Bug within Apache 2.4.18

Stefan, version 1.2.8 works great. Thanks for the fix and for your help. I create a bug report with Apache yesterday. Do you want to update it or would you like me to? https://bz.apache.org/bugzilla/show_bug.cgi?id=59176 On Mon, Mar 14, 2016 at 7:05 AM, Stefan Eissing <

Re: [users@httpd] Potential HTTP/2 Bug within Apache 2.4.18

Russel, if you have a apxs installed, it's probably easiest to checkout and make the github alpha release from https://github.com/icing/mod_h2/releases/tag/v1.2.8 where I just released the fix. There are other bug fixes in there, that should be good to have as well. If you want to stay on the

Re: [users@httpd] Potential HTTP/2 Bug within Apache 2.4.18

I've never applied or tested a patch before, but i'm willing to give it a shot. On Mon, Mar 14, 2016 at 5:35 AM, Stefan Eissing < stefan.eiss...@greenbytes.de> wrote: > > > Am 13.03.2016 um 04:18 schrieb Russel Van Tuyl >: > > > > I'm running an Apache 2.4.18 web

Re: [users@httpd] Potential HTTP/2 Bug within Apache 2.4.18

> Am 13.03.2016 um 04:18 schrieb Russel Van Tuyl : > > I'm running an Apache 2.4.18 web server (Server-A) compiled from source as a > reverse proxy. I'm using ProxyPass on Server-A to pass traffic to a proxy, > nghttpx, listening on 127.0.0.1:3000. This nghttpx proxy