On Sun, 18 Nov 2018 19:41:05 +0200, Niko Tyni wrote:
> Reiterating a bit: the underlying issue with TLSv1.3 seems to be related
> to handling of 'non-application_data_records'.
>
> The client tries to POST but gets an 'SSL wants a read first' error,
> then waits until timeout for the socket to become writable.
>
> A simple way to reproduce it here is
>
> perl -MLWP::UserAgent -e 'LWP::UserAgent->new->post("https://facebook.com";,
> { data => "foo" }) or die'
>
> which deadlocks for me.
I can't reproduce this problem:
% time perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://facebook.com";, { data => "foo" }) or die'
perl -MLWP::UserAgent -e 0.15s user 0.01s system 40% cpu 0.397 total
Has there something changed in LWP::Protocol::https Net::HTTPS
IO::Socket::SSL Net::SSLeay or something else, or is this some local
environment thing?
Also no issue with IPv4-only hosts:
% time perl -MLWP::UserAgent -e
'LWP::UserAgent->new->post("https://twitter.com";, { data => "foo" }) or die'
perl -MLWP::UserAgent -e 0.13s user 0.02s system 36% cpu 0.415 total
Cheers,
gregor, confused, as Guilhem (in message #71) could still reproduce
it at 7 Apr 2019
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06
`. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
`- NP: Furry Lewis: Billy lyons & stack o' lee
signature.asc
Description: Digital Signature
signature.asc
Description: Digital Signature
