Re: openssl from tcl
- From: Alexandre Ferrieux <alexandre.ferrieux@xxxxxxxxx>
- Date: Tue, 1 Apr 2008 14:24:36 -0700 (PDT)
On Apr 1, 6:50 pm, vit...@xxxxxxxxx wrote:
On Apr 1, 9:36 am, USCode <d...@xxxxxxxxx> wrote:
vit...@xxxxxxxxx wrote:
Eric,
I was able to make it work, it was just a matter of sending the
correct sequence of http headers back to the browser.
I used Firefox. There was some extra SSL data that has to be read back
(to clear the buffer) after the browser received and displayed the
response, I didn't dwell much on it, just used "gets $fp" until all
data was absorbed.
It was a good educational experience. I realized that I can't really
use it for anything more than one connection at a time. I can't open a
socket for each incoming connection, so basically it seems pretty
useless for anything serious.
---Victor
Just so I'm clear: You've found you can't use the TLS extension to open
more than 1 SSL socket for each incoming connection at a time?!?! That
doesn't seem right! Can anyone corroborate?
We are not talking about TLS. We are talking about calling the openssl
command from TCL.- Hide quoted text -
If you're always spawning a child binding to the same port, then I'd
say the error is rather between keyboard and chair ;-)
-Alex
.
- References:
- Re: openssl from tcl
- From: vitick
- Re: openssl from tcl
- From: USCode
- Re: openssl from tcl
- From: vitick
- Re: openssl from tcl
- Prev by Date: Re: upvar vs fully qualified
- Next by Date: Re: serving a file to a client --- background fcopy read fileevent event puts socket channel blocking nonblocking
- Previous by thread: Re: openssl from tcl
- Next by thread: Re: openssl from tcl
- Index(es):