On 2017-07-06 14:54, Jacob Champion wrote:
> If I'm honest, my brutally blunt take on it is "stop using HTTP to try
> to emulate push notifications within a single response; pretty much
> everything in the ecosystem is actively working against you at this
> point; responses are designed to be cache
Please find attached patch that removes unused values of io_state_e
enum in mpm_winnt.
--
Ivan Zhakov
Index: server/mpm/winnt/child.c
===
--- server/mpm/winnt/child.c(revision 1801088)
+++ server/mpm/winnt/child.c(working co
For your consideration... pre-release candidate tarballs of
Apache legacy httpd 2.2.34 can be found in;
http://httpd.apache.org/dev/dist/
Thanks all who merged the security work in and other fixes,
and helped identify a couple more lingering defects.
As we picked end of maintenance Jul 1 '17 - t
On Fri, Jun 23, 2017 at 5:19 PM, William A Rowe Jr wrote:
> For your consideration... pre-release candidate tarballs of
> Apache legacy httpd 2.2.33 can be found in;
>
> http://httpd.apache.org/dev/dist/
To make things clear, this call for [VOTE] is withdrawn based
on the regression observed in 2
On 07/06/2017 11:13 AM, Jim Jagielski wrote:
works 4 me...
Doesn't for me. E.g. with a script like
it takes 1 second to receive a single chunk with both lines in it.
From a quick skim I assume this is because we don't use nonblocking
sockets in the proxy implementation. (There's even a not
works 4 me... :/
> On Jul 6, 2017, at 2:08 PM, Helmut K. C. Tessarek
> wrote:
>
> One of the comments on the documentation page of mod_proxy_fcgi
> (http://httpd.apache.org/docs/2.4/mod/mod_proxy_fcgi.html) mentions an
> issue with flush:
>
> There is just no flush support it seems. I attempt
One of the comments on the documentation page of mod_proxy_fcgi
(http://httpd.apache.org/docs/2.4/mod/mod_proxy_fcgi.html) mentions an
issue with flush:
There is just no flush support it seems. I attempt to use PHP flush()
and it won't work until you fill up a buffer first, rendering Server
Sent E
+1 on macOS 10.12.5 and Xcode 8.3.3.
More tests to come ;)
> On Jul 6, 2017, at 1:45 PM, Jim Jagielski wrote:
>
> The pre-release test tarballs for Apache httpd
> version 2.4.27 can be found at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing th
On Thu, Jul 6, 2017 at 12:28 PM, Jacob Champion wrote:
>
> Administrators using prefork who would like to switch to HTTP/2 in the
> future need to understand the limitations of the prefork architecture they
> have selected. And sure, our users can request that we implement a solution
> that "just
The pre-release test tarballs for Apache httpd
version 2.4.27 can be found at the usual place:
http://httpd.apache.org/dev/dist/
I'm calling a VOTE on releasing these as Apache httpd 2.4.27 GA.
[ ] +1: Good to go
[ ] +0: meh
[ ] -1: Danger Will Robinson. And why.
Vote will last the norm
On 07/06/2017 10:09 AM, Reindl Harald wrote:
with removing mpm_prefork support for H2 you kill HTTP2 support for a
lot of production setups which may consider switch to H2 in the future
and for sure not rework there whole configuration but put a proxy like
Trafficserver in front and forget abou
On Thu, Jul 6, 2017 at 12:20 PM, Helmut K. C. Tessarek
wrote:
> On 2017-07-06 13:09, Reindl Harald wrote:
>> with removing mpm_prefork support for H2 you kill HTTP2 support for a
>> lot of production setups which may consider switch to H2 in the future
>> and for sure not rework there whole config
On 2017-07-06 13:09, Reindl Harald wrote:
> with removing mpm_prefork support for H2 you kill HTTP2 support for a
> lot of production setups which may consider switch to H2 in the future
> and for sure not rework there whole configuration but put a proxy like
> Trafficserver in front and forget abo
It starts with a one time warning and will not negotiate. That's all.
> Am 06.07.2017 um 19:02 schrieb William A Rowe Jr :
>
> +1 to removing support of mom prefork. I'd prefer it still start and if
> configured, with an [error] level alert in the logs and simply be disabled.
> Server must sta
Am 06.07.2017 um 19:02 schrieb William A Rowe Jr:
+1 to removing support of mom prefork. I'd prefer it still start and if
configured, with an [error] level alert in the logs and simply be
disabled. Server must start when module is loaded but not configured,
e.g. in test framework, IMO
with
+1 to removing support of mom prefork. I'd prefer it still start and if
configured, with an [error] level alert in the logs and simply be disabled.
Server must start when module is loaded but not configured, e.g. in test
framework, IMO.
On Jul 6, 2017 10:31 AM, "Stefan Eissing"
wrote:
> Correcti
Am 06.07.2017 um 17:28 schrieb Jacob Champion:
On 07/06/2017 07:21 AM, Jim Jagielski wrote:
From IRC:
[10:09:37] I've personally never used apr_table like
described by jchampion_
[10:09:46] and I don't believe it's documented?
[10:10:15] if you want to set a header, you'd use
r.hea
Okey dokey... looks like we are now no longer on hold...
I expect to T&R around 1:30pm eastern, or so.
> On Jul 6, 2017, at 11:13 AM, Jim Jagielski wrote:
>
> Due to the questions around lua and apr_table and the
> change regarding http2 and prefork, doing a T&R of 2.4.27
> right now does not se
> On Jul 6, 2017, at 11:15 AM, Stefan Eissing
> wrote:
>
> Hej,
>
> I tried to gather some discussion about this. Should have polled this mailing
> list. You can read most of it here: https://github.com/icing/mod_h2/issues/142
>
> tl;dr
>
> I had several reports in the past of people being
On 07/06/2017 08:13 AM, Jim Jagielski wrote:
Due to the questions around lua and apr_table and the
change regarding http2 and prefork, doing a T&R of 2.4.27
right now does not seem prudent. I am holding off until
we determine what to do about both "issues"
IMO we are good to go with mod_lua. CH
Correction: websockets are not defined over h2. To make a more "real life"
scenario:
One example is a long polling request by a javascript component. During the
long poll, the browser will not get other responses.
More esoteric: when content filters (brotli, gzip) are in place, compression
hap
On 07/06/2017 07:21 AM, Jim Jagielski wrote:
From IRC:
[10:09:37] I've personally never used apr_table like
described by jchampion_
[10:09:46] and I don't believe it's documented?
[10:10:15] if you want to set a header, you'd use
r.headers_out['foo'] = 'bar'
[10:10:42] so tbh I'd
Hej,
I tried to gather some discussion about this. Should have polled this mailing
list. You can read most of it here: https://github.com/icing/mod_h2/issues/142
tl;dr
I had several reports in the past of people being disappointed about h2
performance, only to learn they were on prefork. Which
Due to the questions around lua and apr_table and the
change regarding http2 and prefork, doing a T&R of 2.4.27
right now does not seem prudent. I am holding off until
we determine what to do about both "issues"
On Thu, Jul 6, 2017 at 10:55 AM, Bert Huijben wrote:
>> *) mod_http2: disable and give warning when mpm_prefork is
>> encountered. The server will
>> continue to work, but HTTP/2 will no longer be negotiated. [Stefan
> Eissing]
>
> Can somebody point me to the reasoning behind this?
>
> I h
> -Original Message-
> From: Jim Jagielski [mailto:j...@jagunet.com]
> Sent: woensdag 5 juli 2017 18:49
> To: dev@httpd.apache.org
> Subject: Re: 2.4.27
>
> These are just the fixes/regressions noted in CHANGES:
>
> Changes with Apache 2.4.27
>
> *) mod_lua: Improve compatibility wit
From IRC:
[10:09:37] I've personally never used apr_table like described by
jchampion_
[10:09:46] and I don't believe it's documented?
[10:10:15] if you want to set a header, you'd use
r.headers_out['foo'] = 'bar'
[10:10:42] so tbh I'd be in favor of just scrapping that bit
[10:10:54]
Thank you Jim.
On Wed, Jul 05, 2017 at 12:48:48PM -0400, Jim Jagielski wrote:
> These are just the fixes/regressions noted in CHANGES:
>
> Changes with Apache 2.4.27
>
> *) mod_lua: Improve compatibility with Lua 5.1, 5.2 and 5.3.
> PR58188, PR60831, PR61245. [Rainer Jung]
>
> *) mod
# testing : code for /modules/lua/setheaders.lua
# expected: 200
# received: '500'
not ok 49
# testing : response content for /modules/lua/setheaders.lua
# expected: ''
# received: 'Error!
# ...httpd-test/framework/t/htdocs/modules/lua/setheaders.lua:4: attempt
to index a nil value (global \'apr_t
The biggest issue, for me, is that currently the
test framework returns loads of errors on mod_lua;
either we "fix" mod_lua or we "fix" the tests but having
it the way it is now is kinda wonky :-)
31 matches
Mail list logo
