Thomas,
the problem is, that closing the in and output ports of an SSL
connection attempts to do a clean shutdown of the SSL connection. This
may sometimes take a while because CHICKEN blocks the thread for I/O
longer than necessary or because the other endpoint of the
communications channel
On 7/11/07, Mark Voortman [EMAIL PROTECTED] wrote:
Folks,
I just ran into a problem with the openssl egg. If I run the code below
and browse to https://localhost/ it shows the certificate and everything,
but the page keeps loading. Only when I kill the server it actually shows
the page. My
Does adding a Connection: close change anything?
Nice idea, but it didn't help.
Cheers,
Mark
___
Chicken-users mailing list
Chicken-users@nongnu.org
http://lists.nongnu.org/mailman/listinfo/chicken-users
Mark Voortman wrote:
[...]
I just ran into a problem with the openssl egg. If I run the code below
and browse to https://localhost/ it shows the certificate and everything,
but the page keeps loading.
[...]
Hello,
please try the new version of the openssl egg which I have just uploaded
to
Folks,
I just ran into a problem with the openssl egg. If I run the code below
and browse to https://localhost/ it shows the certificate and everything,
but the page keeps loading. Only when I kill the server it actually shows
the page. My guess is that close-input-port and close-output-port
Hi Mark,
On Wed, 11 Jul 2007 10:30:08 -0400 (EDT) Mark Voortman [EMAIL PROTECTED]
wrote:
I just ran into a problem with the openssl egg. If I run the code below
and browse to https://localhost/ it shows the certificate and everything,
but the page keeps loading. Only when I kill the server
On 11 Jul 2007 12:01:30 -0300, Mario Domenech Goulart [EMAIL PROTECTED]
A random thought: isn't it a buffering problem? In case it makes
sense, take a look at
http://chicken.wiki.br/Unit%20posix#set-buffering-mode!
I don't think so - closing the port should flush all remaining output.
Mark Voortman wrote:
[...]
I just ran into a problem with the openssl egg. If I run the code below
and browse to https://localhost/ it shows the certificate and everything,
but the page keeps loading. Only when I kill the server it actually shows
the page. My guess is that close-input-port
