Sorry this is such a late response as it makes understanding the root of the problem more difficult. Nevertheless...
The reason why I posted my test case with curl is that I was experiencing the problem in web browsers as well as in curl. It was easier to demonstrate my problem with curl than with a web browser. So... looking back to this problem it now no longer is a problem. Perl and all modules reported by mojo version have been updated. $ mojo version CORE Perl (v5.18.1, linux) Mojolicious (4.65, Top Hat) OPTIONAL EV 4.0+ (4.15) IO::Socket::IP 0.16+ (0.24) IO::Socket::SSL 1.75+ (1.962) This version is up to date, have fun! I'm pretty sure I didn't upgrade my curl, but I don't know. Nevertheless, since curl was challenged as a bug, here's the version I'm using this time: $ curl -V curl 7.32.0 (x86_64-pc-linux-gnu) libcurl/7.32.0 OpenSSL/1.0.1e zlib/1.2.8 libidn/1.28 librtmp/2.3 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp smtp smtps telnet tftp Features: AsynchDNS GSS-Negotiate IDN IPv6 Largefile NTLM NTLM_WB SSL libz TLS-SRP Now, I get responses from curl that I expect: $ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 hi$ curl -k https://localhost:4022 On Sun, Sep 1, 2013 at 9:15 PM, Charlie Brady < [email protected]> wrote: > > > On Fri, 30 Aug 2013, Stefan Adams wrote: > > > I'm running an extremely simple mojo app on Hypnotoad with 20 workers > and 1 > > client connection. It's listening on http and https. > > > > If I curl the http address a dozen times in quick succession, each > request > > gives me an expected response. > > > > If I curl the https address a dozen times in quick succession, I > sometimes > > get the expected response and sometimes get no response at all. > > > > The times that it fails, curl -v reports: > > * SSL read: error:00000000:lib(0):func(0):reason(0), errno 104 > > Maybe it's a curl bug: > > http://sourceforge.net/p/curl/bugs/1099/ > > > > > Here's the uber-small app: > > > > $ cat test.pl > > use Mojolicious::Lite; > > app->config(hypnotoad => {workers=>20, clients=>1, listen=>['http:// > > *:4021','https://*:4022'], proxy=>1}); > > get '/' => {text=>'hi'}; > > app->start; > > $ hypnotoad test.pl > > > > $ mojo version > > CORE > > Perl (v5.18.0, linux) > > Mojolicious (4.28, Top Hat) > > > > OPTIONAL > > EV 4.0+ (4.15) > > IO::Socket::IP 0.16+ (0.22) > > IO::Socket::SSL 1.75+ (1.953) > > > > And this demonstrates the results (just pressed <UP>, <ENTER> over and > > over): > > $ curl -k https://localhost:4022 > > $ curl -k https://localhost:4022 > > $ curl -k https://localhost:4022 > > $ curl -k https://localhost:4022 > > hi$ curl -k https://localhost:4022 > > hi$ curl -k https://localhost:4022 > > hi$ curl -k https://localhost:4022 > > $ curl -k https://localhost:4022 > > $ curl -k https://localhost:4022 > > hi$ curl -k https://localhost:4022 > > hi$ curl -k https://localhost:4022 > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Mojolicious" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/mojolicious. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/groups/opt_out.
