On Wed, Jul 22, 2015 at 11:58 AM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
Hmm, that would mean first come, first negotiated?
There are RUN_FIRST (e.g. handler and translate_name) and RUN_ALL
(e.g. fixups and pre_connection) flavors of the hook functions.
So, a RUN_ALL that collects willing protocols pre_select, a ALL for post_select
and a FIRST for switch?
Am 22.07.2015 um 18:02 schrieb Eric Covener cove...@gmail.com:
On Wed, Jul 22, 2015 at 11:58 AM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
Hmm, that would mean first come,
On Mon, Jul 20, 2015 at 4:07 PM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
Key points:
- Integrates TLS+ALPN and HTTP/1 Upgrade: header
- Allows upgrades on clean connection and in the middle of a request.
Implementors might chose to only support one or the other or both
- Protocol
Hmm, that would mean first come, first negotiated?
Am 22.07.2015 um 17:13 schrieb Yann Ylavic ylavic@gmail.com:
On Mon, Jul 20, 2015 at 4:07 PM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
Key points:
- Integrates TLS+ALPN and HTTP/1 Upgrade: header
- Allows upgrades on clean
On Wed, Jul 22, 2015 at 6:42 PM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
So, a RUN_ALL that collects willing protocols pre_select, a ALL for
post_select
post_select is to announce the selected one, right?
That looks good to me.
and a FIRST for switch?
Isn't the core doing the
Am 22.07.2015 um 19:00 schrieb Yann Ylavic ylavic@gmail.com:
On Wed, Jul 22, 2015 at 6:42 PM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
So, a RUN_ALL that collects willing protocols pre_select, a ALL for
post_select
post_select is to announce the selected one, right?
That
On Wed, Jul 22, 2015 at 9:37 PM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
Am 22.07.2015 um 19:00 schrieb Yann Ylavic ylavic@gmail.com:
On Wed, Jul 22, 2015 at 6:42 PM, Stefan Eissing
stefan.eiss...@greenbytes.de wrote:
So, a RUN_ALL that collects willing protocols pre_select, a
I have been installing Bundle::ApacheTest on AIX 5.3, with perl-5.8.2 and
the tests seem to be working normally for me.
There have been some // comment errors pop-up in a few mods, and a define
that AIX does not like with a few mods. But other than those typos the only
problem I have had is with
My OS X setup, may it help find the cause of problems:
- httpd/trunk built with prefix/opt/apachte-trunk
with --*really*-build-and-load-all-modules and then
all but one mpm commented out
- test/framework/trunk build with /opt/apache-trunk/bin/apxs
all extra modules installed/updated with
Nothing stands out... weird. I may try compiling on my own.
System Perl:
Compiler:
cc='cc', ccflags ='-arch x86_64 -arch i386 -g -pipe -fno-common
-DPERL_DARWIN -fno-strict-aliasing -fstack-protector',
optimize='-Os',
cppflags='-g -pipe -fno-common -DPERL_DARWIN
On 07/21/2015 04:07 PM, Yann Ylavic wrote:
On Tue, Jul 21, 2015 at 2:50 PM, Plüm, Rüdiger, Vodafone Group
ruediger.pl...@vodafone.com wrote:
I would go for 2.
+1
Done in http://svn.apache.org/r1692258.
Regards,
Jan Kaluza
On Jul 22, 2015, at 8:21 AM, Kevin A. McGrail kmcgr...@pccc.com wrote:
On 7/22/2015 6:43 AM, Jim Jagielski wrote:
Nothing stands out... weird. I may try compiling on my own.
Well, the gccversion is different.
clang-600.0.54 v clang-600.0.39
I doubt that's causing the problem.
In any
On 7/22/2015 6:43 AM, Jim Jagielski wrote:
Nothing stands out... weird. I may try compiling on my own.
Well, the gccversion is different.
clang-600.0.54 v clang-600.0.39
Regards,
KAM
13 matches
Mail list logo
