Re: svn commit: r1791807 - /httpd/httpd/trunk/docs/conf/extra/httpd-manual.conf.in

* William A Rowe Jr wrote: > On Tue, Apr 18, 2017 at 3:56 PM, André Malo wrote: > > * wr...@apache.org wrote: > >> Author: wrowe > >> Date: Tue Apr 18 16:25:03 2017 > >> New Revision: 1791807 > >> > >> URL: http://svn.apache.org/viewvc?rev=1791807=rev > >> Log: > >> KISS:

Re: Fixing more OpenSSL callback crashes

On 04/12/2017 11:34 AM, Jacob Champion wrote: It's probably worth noting at this point that, even if is unsafe: - Windows and BeOS users are still handled explicitly by default in 1.0.x. - If OpenSSL still provides the deprecated CRYPTO_set_id_callback(), we can use it instead. We're not

Re: svn commit: r1674661 - in /httpd/httpd/branches/2.4.x: ./ CHANGES STATUS modules/proxy/mod_proxy_wstunnel.c

On Wed, Apr 19, 2017 at 4:41 AM, jean-frederic clere wrote: > So I need 2 things: > 1 - Upgrade to jboss-remoting. > 2 - Proxy without the upgrade header. Okay, I don't think we had any way to know the module was being used for either of these things.A new directive will

AW: svn commit: r1674661 - in /httpd/httpd/branches/2.4.x: ./ CHANGES STATUS modules/proxy/mod_proxy_wstunnel.c

I guess the patch is fine with one exception: Please do not "recycle" a configuration option setup explicitly for another module (flusher for mod_proxy_fdpass) for your patch. This only creates confusion. Please create a new one and document it. Regards Rüdiger > -Ursprüngliche

Re: hanging apache httpd processes due to mod_h2

Thanks, the backtraces really helped. Could you try the following patch? -Stefan h2_beam_locks_v1.diff Description: Binary data > Am 19.04.2017 um 08:32 schrieb Stefan Priebe - Profihost AG > : > > Hi Stefan, > > this is now with v1.10.2 but it does not help. > >

Re: svn commit: r1674661 - in /httpd/httpd/branches/2.4.x: ./ CHANGES STATUS modules/proxy/mod_proxy_wstunnel.c

On 03/02/2017 12:50 PM, Eric Covener wrote: > Curious about the headers in the bug report / recreate. I have looked to the problem again I have 2 JIRA related to the commit: https://issues.jboss.org/browse/JBCS-254 https://issues.jboss.org/browse/JBCS-291 Basically people using

Re: drop experimental from http2 for 2.4.next?

Do we foresee an issue w/ it moving to RTC? I don't... I think we could get the required 3 +1s quite easily. > On Apr 18, 2017, at 2:35 PM, Eric Covener wrote: > > On Sat, Apr 15, 2017 at 8:15 PM, Nick Kew wrote: >> Why would it be good for a stable (i.e.

Re: [users@httpd] Problem when using nested if statements in apache 2.4

2017-03-27 19:09 GMT+02:00 Luca Toscano : > Hi Yann, > > 2017-03-27 8:56 GMT+02:00 Yann Ylavic : > >> Hi Luca, >> >> On Mon, Mar 20, 2017 at 1:25 PM, Luca Toscano >> wrote: >> > >> > Documentation updated with the current

ProxyWebsocketIdleTimeout no log message

Hi, testing mod_proxy_wstunnel from trunk I encountered a connection close on client-side due to an idle timeout. I needed some time to identify the problem as there was no log message written. Also the status code 200 in the access_log was misleading. Studying the code I now understand why

Re: hanging apache httpd processes due to mod_h2

Hi Stefan, this is now with v1.10.2 but it does not help. PID old gen: 2 15608 yes (old gen) 2 no 0 0 0 0 0 requests in G state: 2-2 15608 4/36/36 G 252.75 30695 41 22.10.870.87 A.B.C.D h2 XYZ:443 GET