[cl-plus-ssl-devel] concurrency problems when used with chrome?

[Attila Lendvai]

hi,

> What is your platform (OS and Lisp impl)? Any other details you think relevant?


sorry for the lack of info, here are some details:

linux x86-64
sbcl HEAD
cl+ssl HEAD

the patch/codebase:
http://dwim.hu/darcsweb/darcsweb.cgi?r=HEAD%20hu.dwim.web-server;a=commitdiff;h=20110508155430-6b9e8-e8acc1263090fd222b2f8014ec5a9490173d7d13.gz


> As a workaround, until the problem is fixed, you may need to use a reverse proxy like
> nginx for https.


yeah, i know i could set up a proxy, but i'd like to run
http://dwim.hu as a full-lisp server. it's a non-paying project, so
there's no pressure on https (as of now), i just want to have that,
too.

i'll read up on the threading issue, thanks for the pointer!

until then, it seems like something happens different at accepting the
connections than it happens with plain http.

the multiplexer on the listen fd seems to return more often than with
plain http, although it's a simple static file being served. with http
there are only two read events returned (+1 for the favicon.ico
unconditionally tried by chrome for every request), but with https i
see some 6-10 log lines about a read event on the listen fd.

probably many of those are stale and i get the before mentioned error
because of that. the fact that besides the errors on the server,
things seems to work fine in the browser also suggests this.

any ideas why i get more read events on the listen fd?

does the certificate exchange happen on a separate connection?

or is there a document on ssl that i should read to stop asking silly
questions? :)

thanks for all the help,

-- 
 attila

Notice your eroding (digital) freedom, and do something about it!

PGP: 2FA1 A9DC 9C1E BA25 A59C  963F 5D5F 45C7 DFCD 0A39
OTR XMPP: 8647EEAC EA30FEEF E1B55146 573E52EE 21B1FF06
BitCoin: 154uf86Vd9rpjMULd9CXa7nVwikknYZJiB