Le 22/10/2018 à 16:56, Jim Jagielski a écrit :
The latest update to usertrack works. Thx! speling still bad:
On httpd-2.4 HEAD:
t/modules/speling.t . 1/48 # Failed test 11 in
t/modules/speling.t at line 46 fail #6
# Failed test 12 in t/modules/speling.t at line 50
Le 22/10/2018 à 16:16, Rainer Jung a écrit :
Am 22.10.2018 um 15:45 schrieb Yann Ylavic:
On Mon, Oct 22, 2018 at 3:28 PM Yann Ylavic
wrote:
On Mon, Oct 22, 2018 at 3:09 PM Jim Jagielski wrote:
These are new from a coupla day ago:
Both tests were added a few days ago, so probably not
Well, we'll see if other macOS users also have the same failures... that will
determine if my hypothesis is correct.
> On Oct 22, 2018, at 11:37 AM, Stefan Eissing
> wrote:
>
> dAMn! uSABilitY StRiks aGAIn!
>
>> Am 22.10.2018 um 17:34 schrieb Jim Jagielski :
>>
>> OK, I think I know what
dAMn! uSABilitY StRiks aGAIn!
> Am 22.10.2018 um 17:34 schrieb Jim Jagielski :
>
> OK, I think I know what may be happening; I am guessing its due to the macOS
> file system being case insensitive but case preserving...
OK, I think I know what may be happening; I am guessing its due to the macOS
file system being case insensitive but case preserving...
Hi, Cory;
Yes, you are correct. This gets cleaned up as part of the final
fixups in the release scripts. It's one of the things done at the last
moment :-)
--
Daniel Ruggeri
On 2018-10-22 10:23, Cory McIntire wrote:
Just a note, the date here is Sept instead of Oct :)
Just a note, the date here is Sept instead of Oct :)
http://httpd.apache.org/dev/dist/Announcement2.4.html
http://httpd.apache.org/dev/dist/Announcement2.4.txt
(I realize this might not be final version of said text.. just wanted to
mention)
Thanks
Cory McIntire
Release Manager - EasyApache
The latest update to usertrack works. Thx! speling still bad:
On httpd-2.4 HEAD:
t/modules/speling.t . 1/48 # Failed test 11 in
t/modules/speling.t at line 46 fail #6
# Failed test 12 in t/modules/speling.t at line 50 fail #5
# Failed test 35 in t/modules/speling.t at line
On Sat, Oct 20, 2018 at 6:28 AM Rainer Jung wrote:
>
> - Net::SSLeay 1.86_06 tag from Github
> https://github.com/radiator-software/p5-net-ssleay.git. Added "-ldl
> -pthread" to OTHERLDFLAGS in Makefile. It contains the plumbing needed
> for some new 1.1.1 APIs.
With this change (and all the
Am 22.10.2018 um 15:45 schrieb Yann Ylavic:
On Mon, Oct 22, 2018 at 3:28 PM Yann Ylavic wrote:
On Mon, Oct 22, 2018 at 3:09 PM Jim Jagielski wrote:
These are new from a coupla day ago:
Both tests were added a few days ago, so probably not a regression
(test issues likely).
FWIW, both
On 2018-10-18 09:36, Daniel Ruggeri wrote:
Hi, all;
Please find below the proposed release tarball and signatures:
https://dist.apache.org/repos/dist/dev/httpd/
I would like to call a VOTE over the next few days to release this
candidate tarball as 2.4.37:
[ ] +1: It's not just good, it's
On Mon, Oct 22, 2018 at 3:28 PM Yann Ylavic wrote:
>
> On Mon, Oct 22, 2018 at 3:09 PM Jim Jagielski wrote:
> >
> > These are new from a coupla day ago:
>
> Both tests were added a few days ago, so probably not a regression
> (test issues likely).
FWIW, both pass on my Linux system.
On Mon, Oct 22, 2018 at 3:09 PM Jim Jagielski wrote:
>
> These are new from a coupla day ago:
Both tests were added a few days ago, so probably not a regression
(test issues likely).
Thanks a lot!
> Am 22.10.2018 um 14:06 schrieb Rainer Jung :
>
> This seems to work nicely, committed in r1844546. Tests with old OpenSSL
> either in client or server result in TLSv1 and disable h2 tests. TLS test
> requests that result in TLSv1_2 or TLSv1_3 enable h2 tests.
>
> Regards,
>
>
These are new from a coupla day ago:
t/modules/speling.t . 1/48 # Failed test 11 in
t/modules/speling.t at line 46 fail #6
# Failed test 12 in t/modules/speling.t at line 50 fail #5
# Failed test 35 in t/modules/speling.t at line 46 fail #18
# Failed test 36 in
This seems to work nicely, committed in r1844546. Tests with old OpenSSL
either in client or server result in TLSv1 and disable h2 tests. TLS
test requests that result in TLSv1_2 or TLSv1_3 enable h2 tests.
Regards,
Rainer
Am 22.10.2018 um 12:37 schrieb Rainer Jung:
I wonder whether it would
I wonder whether it would be easier to check whether a TLS connection
uses TLS 1.2 or later and disable the h2 test if not.
Nevertheless the module for checking the server version might be useful,
but here I guess checking the TLS version is more appropriate.
But that might mean, that the
Can anyone comment on the below, especially whether this test should be
disabled when used with TLS 1.3 (modern access) and whether it is OK (a
wrong test definition) for 1.3 to actually handle the prefix attack request?
Regards,
Rainer
Am 20.10.2018 um 08:16 schrieb Rainer Jung:
Test
18 matches
Mail list logo
