RE: 2.5 alpha proposal

> -Original Message- > From: William A Rowe Jr [mailto:wr...@rowe-clan.net] > Sent: donderdag 16 november 2017 16:40 > To: httpd > Subject: Re: 2.5 alpha proposal > > On Thu, Nov 16, 2017 at 8:40 AM, Stefan Eissing > wrote: > >> Am

RE: Serf support in trunk

> -Original Message- > From: Rainer Jung [mailto:rainer.j...@kippdata.de] > Sent: maandag 20 november 2017 14:33 > To: dev@httpd.apache.org; Bert Huijben <b...@qqmail.nl> > Cc: d...@serf.apache.org > Subject: Re: Serf support in trunk > > I have no idea w

RE: Serf support in trunk

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: maandag 20 november 2017 11:40 > To: dev@httpd.apache.org > Subject: Re: Serf support in trunk > > +1 for pulling it unless someone steps forward. > > > Am 19.11.2017 um 12:49 schrieb Rainer Jung

RE: httpd memory consumption

> -Original Message- > From: Ruediger Pluem [mailto:rpl...@apache.org] > Sent: vrijdag 6 oktober 2017 09:47 > To: Apache HTTP Server Development List > Subject: httpd memory consumption > > I am currently looking at a core of a httpd 2.4 process using the event

RE: 2.4.27

> -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

RE: Upgrade Summary

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: vrijdag 11 december 2015 10:20 > To: dev@httpd.apache.org > Subject: Re: Upgrade Summary > Regarding request bodies: > - websocket will never switch on request bodies > - h2c currently does not, but

RE: Upgrade Summary

If you request an upgrade to TLS on your initial request, upgrading with a body might still make sense. Especially if the server would respond with a 401. But also if the request can be public, but the response needs to be secured. If we blindly ignore the upgrade as ‘doesn’t make sense’, the

RE: Upgrade Summary

from Mail for Windows 10 From: Yann Ylavic Sent: zaterdag 12 december 2015 01:46 To: Bert Huijben Subject: Re: Upgrade Summary On Sat, Dec 12, 2015 at 12:48 AM, Bert Huijben <b...@qqmail.nl> wrote: > If you request an upgrade to TLS on your initial request, upgrading with a > body migh

RE: Upgrade Summary

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: donderdag 10 december 2015 11:47 > To: dev@httpd.apache.org > Subject: Re: Upgrade Summary > > Given all the input on this thread, I arrive at the following pseudo code: > > 1. Post Read Request

RE: Upgrade Summary

Great to see where this discussion is headed: +1 on the last design ideas. Going with one ‘as early as possible’ upgrade and one ‘upgrade last’ should handle all these cases just fine. I don’t think the h2c and TLS cases really have to be that different as suggested in the earlier parts

RE: Upgrade Summary

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: dinsdag 8 december 2015 11:55 > To: dev@httpd.apache.org > Subject: Re: Upgrade Summary > > > > Am 08.12.2015 um 11:44 schrieb Yann Ylavic : > > > > On Tue, Dec 8, 2015 at

RE: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl Upgrade tls

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: dinsdag 8 december 2015 10:25 > To: dev@httpd.apache.org > Subject: Re: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl > Upgrade tls > > > > Am 08.12.2015 um 01:58 schrieb William A Rowe Jr

RE: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl Upgradetls

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: dinsdag 8 december 2015 10:43 > To: dev@httpd.apache.org > Subject: Re: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl > Upgradetls > If Apache accepts body lengths of up to 64KB (or

RE: Upgrade Summary

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: dinsdag 8 december 2015 12:41 > To: dev@httpd.apache.org > Subject: RE: Upgrade Summary > > I don't think we should require all auth to happen on HTTP/1.1. If you want to go for equiv

RE: Upgrade Summary

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: dinsdag 8 december 2015 13:22 > To: dev@httpd.apache.org > Subject: Re: Upgrade Summary > > > > Am 08.12.2015 um 12:40 schrieb Bert Huijben <b...@qqmail.n

RE: Upgrade Summary

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: dinsdag 8 december 2015 11:07 > To: dev@httpd.apache.org > Subject: Upgrade Summary > > Trying to summarize the status of the discussion and where the issues are > with the current Upgrade

RE: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl Upgradetls

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: dinsdag 8 december 2015 11:36 > To: dev@httpd.apache.org > Subject: Re: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl > Upgradetls > > Bert, > > I do not understand. How do you want to

RE: Upgrade Summary

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: dinsdag 8 december 2015 13:54 > To: dev@httpd.apache.org > Subject: Re: Upgrade Summary > > I see. Delta-V goodies. > > My proposal therefore is: > - keep the upgrade/protocol switch mechanism as is

RE: AW: 2.4 pause - mod_http2 patchset Upgrade h2c vs mod_ssl Upgradetls

Is this a h2 limitation or a mod_h2 limitation? If I would like h2c upgrade from Subversion without an additional request I would have to send the upgrade request with a very short OPTIONS request that has a body. The way I read the spec that should be possible if both sides go through all

RE: No H2 Window updates!

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: vrijdag 4 december 2015 10:18 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > That is unfortunate. I added a test case which reproduced window > exhaustion before I fixed it. What

RE: No H2 Window updates!

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: vrijdag 4 december 2015 16:23 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > If you find the time, the lastest v1.0.10 mod_http2 in 2.4.x sets the > connection window to max

RE: svn commit: r1717970 - /httpd/test/mod_h2/trunk/test/test_window_update.sh

> -Original Message- > From: ic...@apache.org [mailto:ic...@apache.org] > Sent: vrijdag 4 december 2015 15:26 > To: c...@httpd.apache.org > Subject: svn commit: r1717970 - > /httpd/test/mod_h2/trunk/test/test_window_update.sh > > Author: icing > Date: Fri Dec 4 14:25:53 2015 > New

RE: svn commit: r1717970 - /httpd/test/mod_h2/trunk/test/test_window_update.sh

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: vrijdag 4 december 2015 18:51 > To: dev@httpd.apache.org > Subject: RE: svn commit: r1717970 - > /httpd/test/mod_h2/trunk/test/test_window_update.sh > > > > > -O

RE: No H2 Window updates! (Probably a Serf issue!)

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: vrijdag 4 december 2015 21:45 > To: dev@httpd.apache.org > Subject: RE: No H2 Window updates! > > > > > -Original Message- > > From: Stefan Eissing [mailto:stefan.eiss

RE: No H2 Window updates! (Probably a Serf issue!)

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: vrijdag 4 december 2015 22:27 > To: dev@httpd.apache.org > Subject: RE: No H2 Window updates! (Probably a Serf issue!) > > > > > -Original Message- > > From: Bert Huij

RE: No H2 Window updates!

. Which doesn't fit, because the total outgoing window has to fit in 2^31-1... See the RFC. That is all that happens. (The windowing in the other direction is completely uninteresting here... as it happens completely independent) Bert > > > Am 04.12.2015 um 18:42 schrieb Bert

RE: reverse proxy wishlist

> -Original Message- > From: Jim Jagielski [mailto:j...@jagunet.com] > Sent: donderdag 3 december 2015 22:20 > To: dev@httpd.apache.org > Subject: Re: reverse proxy wishlist > > > > On Dec 3, 2015, at 11:09 AM, William A Rowe Jr > wrote: > > > > On Thu, Dec 3,

RE: No H2 Window updates!

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: woensdag 2 december 2015 15:45 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > Please find with r1717641 version 1.0.9-DEV of mod_http2 in trunk and > branches/2.4.x > that fixes

RE: No H2 Window updates!

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: zondag 29 november 2015 09:04 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > Ok, thanks. I think I have an idea of what's happening: > - on short request bodies, window updates

RE: No H2 Window updates!

> -Original Message- > From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] > Sent: vrijdag 27 november 2015 22:35 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > Bert Huijben in gmane.comp.apache.devel (Fri, 27 Nov 2015 20:04:14 +0100): > >Well.

RE: No H2 Window updates!

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: zaterdag 28 november 2015 13:01 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > I am not really here, but... > > the window updates are sent out via update_window(), line 1001,

RE: No H2 Window updates!

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: zaterdag 28 november 2015 13:01 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > I am not really here, but... > > the window updates are sent out via update_window(), line 1001,

RE: No H2 Window updates!

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: zaterdag 28 november 2015 13:01 > To: dev@httpd.apache.org > Subject: Re: No H2 Window updates! > > I am not really here, but... > > the window updates are sent out via update_window(), line 1001,

RE: No H2 Window updates!

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: zaterdag 28 november 2015 14:09 > To: stefan.eiss...@greenbytes.de; dev@httpd.apache.org > Subject: RE: No H2 Window updates! > > > > > -Original Message- > > From

RE: No H2 Window updates!

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: zaterdag 28 november 2015 14:32 > To: stefan.eiss...@greenbytes.de; dev@httpd.apache.org > Subject: RE: No H2 Window updates! > In case of Subversion's real usage, I want to commit potentially h

RE: No H2 Window updates!

Well… it is not a regression, so can it be a show stopper? ☺… But I would like to see this fixed. I have no idea how hard it would be to fix this though. It could be as simple as removing that config line (which was probably added somewhere early on if I look at that comment). But windowing

No H2 Window updates!

Hi, I finally took the time to diagnose that segfault I had, and I think it points to a serious bug in httpd. To summarize this: I don't receive window updates. In this specific test we set a very huge amount of small requests (bodies of 95 and 113 bytes), until we get

RE: No H2 Window updates!

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: vrijdag 27 november 2015 13:56 > To: b...@qqmail.nl > Subject: > >     Hi, > > I finally took the time to diagnose that segfault I had, and I think it > po

RE: H2 stream dependencies

> -Original Message- > From: Bert Huijben [mailto:b...@qqmail.nl] > Sent: woensdag 25 november 2015 22:45 > To: dev@httpd.apache.org > Subject: RE: H2 stream dependencies > * 2 of these are related to HTTP/1.1 status lines where we no longer have > access to th

RE: H2 stream dependencies

> -Original Message- > From: Jan Ehrhardt [mailto:php...@ehrhardt.nl] > Sent: donderdag 26 november 2015 19:20 > To: dev@httpd.apache.org > Subject: Re: H2 stream dependencies > > Bert Huijben in gmane.comp.apache.devel (Thu, 26 Nov 2015 18:36:00 > +0100): >

RE: apr_token_* conclusions (was: Better casecmpstr[n]?)

The example was the other way around. Changing SS to ß is not a valid transform, but the other way is. There are also transforms on the combined AE characters, etc. That Turkish ‘I’ problem is the only case I know of where the collation actually changes behavior within the usual western

RE: apr_token_* conclusions (was: Better casecmpstr[n]?)

See http://www.siao2.com/2004/12/03/274288.aspx And http://www.siao2.com/2013/04/04/10407543.aspx For some background and related bugs in several products. I hope this blog will stay alive. (The author passed away recently) Bert From: Bert Huijben [mailto:b

RE: apr_token_* conclusions (was: Better casecmpstr[n]?)

We have a set of similar comparison functions in Subversion. I’m pretty sure we already had these in the time we still had ebcdic support on trunk. (We removed that support years ago, but the code should still live on a branch) Bert From: William A Rowe Jr [mailto:wr...@rowe-clan.net]

RE: H2 stream dependencies

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: woensdag 25 november 2015 10:05 > To: dev@httpd.apache.org > Subject: Re: H2 stream dependencies > > The execution order of requests is not defined by the protocol and up to the > server

RE: H2 stream dependencies

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: vrijdag 20 november 2015 10:26 > To: dev@httpd.apache.org > Subject: Re: H2 stream dependencies > > Bert, > > interesting and nice to see the progress. You probably could use priorities > for >

RE: svn commit: r1715363 - in /httpd/httpd/trunk/modules/http2: h2_request.c h2_response.h h2_session.c h2_stream.c h2_stream.h h2_util.c h2_util.h

> -Original Message- > From: Jim Jagielski [mailto:j...@jagunet.com] > Sent: vrijdag 20 november 2015 17:04 > To: dev@httpd.apache.org > Subject: Re: svn commit: r1715363 - in /httpd/httpd/trunk/modules/http2: > h2_request.c h2_response.h h2_session.c h2_stream.c h2_stream.h > h2_util.c

RE: H2 stream dependencies

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: vrijdag 20 november 2015 10:26 > To: dev@httpd.apache.org > Subject: Re: H2 stream dependencies > > Bert, > > interesting and nice to see the progress. You probably could use priorities > for >

RE: svn commit: r1715294 - /httpd/httpd/trunk/server/core.c

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: vrijdag 20 november 2015 10:11 > To: dev@httpd.apache.org > Subject: Re: svn commit: r1715294 - /httpd/httpd/trunk/server/core.c > > +1 for lowercasing and pls backport, since it just arrived as is

H2 stream dependencies

Hi All (and Stefan in particular), As already noted I'm trying to make Subversion work over http/2 via the Apache Serf library. Today I made a few huge steps forward and got most of the Subversion tests working over h2. (Just +- 60 failures left of the +- 2000 tests) One

RE: svn commit: r1714219 - in /httpd/httpd/trunk: docs/manual/mod/ modules/http2/

> -Original Message- > From: ic...@apache.org [mailto:ic...@apache.org] > Sent: vrijdag 13 november 2015 15:54 > To: c...@httpd.apache.org > Subject: svn commit: r1714219 - in /httpd/httpd/trunk: docs/manual/mod/ > modules/http2/ > > Author: icing > Date: Fri Nov 13 14:54:15 2015 > New

RE: [openssl-dev] [openssl.org #4145] Enhancement: patch to support s_client -starttls http

Hi William, Is any commonly used client actually implementing this spec in a way that makes this RFC relevant for httpd? Sure we could implement this… Perhaps we already did but once you switch to TLS there are so many security related things to account for. Ignoring

RE: mod_http2 / H2WindowSize default

> -Original Message- > From: Yann Ylavic [mailto:ylavic@gmail.com] > Sent: dinsdag 17 november 2015 00:49 > To: httpd-dev <dev@httpd.apache.org> > Subject: Re: mod_http2 / H2WindowSize default > > On Mon, Nov 16, 2015 at 8:23 PM, Bert Hui

RE: mod_http2 / H2WindowSize default

> -Original Message- > From: Stefan Eissing [mailto:stefan.eiss...@greenbytes.de] > Sent: maandag 16 november 2015 12:41 > To: dev@httpd.apache.org > Subject: Re: mod_http2 / H2WindowSize default > > > > Am 14.11.2015 um 11:14 schrieb B

mod_http2 / H2WindowSize default

Hi, I was wondering why mod_http2 currently uses a default window size of 65536. The http2 protocol defines a default window size of 65535, just 1 byte less than the current default. Changing the default requires transferring this setting to every client in the initial

RE: h1/h2/h2c throughput numbers

setup. Hi Stefan, Thanks for all your work on this. I'm currently working on adding http/2 support to Apache Serf, and 2.4.17 provides an easy to use test target for me :) Good to see the progress here. I hope to start testing Subversion over http/2 soon. Thanks, Bert Huijben -- Subversion, Serf, AnkhSVN, SharpSvn, SharpGit, ...

RE: ALPN patch comments

Can we really do ALPN per vhost? If this is handled before or at the same time as SNI, then SSLAlpnEnable is eventually applied per listening address, while H2Engine would make sense even for multiple hosts at the same ip. I would say returning some error is a valid response for not

RE: Looking for a release of 2.4.x soonish

-Original Message- From: Jim Jagielski [mailto:j...@jagunet.com] Sent: dinsdag 24 juni 2014 20:40 To: httpd Subject: FYI: Looking for a release of 2.4.x soonish I'm hoping to encourage us to push out the next 2.4 release within the next coupla weeks, maybe after the July 4th

RE: [Patch] non blocking writes in core

-Original Message- From: Graham Leggett [mailto:minf...@sharp.fm] Sent: dinsdag 19 november 2013 18:44 To: dev@httpd.apache.org Subject: Re: [Patch] non blocking writes in core On 18 Nov 2013, at 1:24 PM, Plüm, Rüdiger, Vodafone Group ruediger.pl...@vodafone.com wrote: +

Playing with cmake: LONG_NAME= problems

Hi, As I already mentioned I'm re-scripting my build of httpd to work using the new cmake generator. It looks like I have things working now, with about half as many local patches as before..., but I think one problem I had to patch around will be common for everybody using project files

RE: Playing with cmake: LONG_NAME= problems

Trawick [mailto:traw...@gmail.com] Sent: maandag 18 november 2013 19:22 To: Apache HTTP Server Development List Subject: Re: Playing with cmake: LONG_NAME= problems On Mon, Nov 18, 2013 at 12:37 PM, Bert Huijben b...@qqmail.nl mailto:b...@qqmail.nl wrote: Hi, As I already mentioned I'm re

RE: Playing with cmake: LONG_NAME= problems

On Mon, Nov 18, 2013 at 4:14 PM, Jeff Trawick traw...@gmail.com mailto:traw...@gmail.com wrote: On Mon, Nov 18, 2013 at 4:10 PM, Bert Huijben b...@qqmail.nl mailto:b...@qqmail.nl wrote: Hi Jeff, Thanks for looking into this. I tried the Visual Studio 9 and Visual Studio 11

r1542328 breaks cmake build

Hi, I'm trying to switch my personal Windows build from the old system to cmake in preparation for the next 2.4 tag and my build of httpd started to work until r1542328 removed a file that is still referenced from CMakeLists.txt. Can somebody with enough karma remove the