- From: <erikvcl@silcom.com>
- Date: Wed, 1 Oct 2003 13:28:48 -0700 (PDT)
- To: www-lib@w3.org
Hi, I'll answer my own question here. HTSSLhttps_init(NO) is the setting I should use. I found the answer on the mailing list archives. It seems as though LOTS of people had this question. Erik. On Tue, 30 Sep 2003 erikvcl@silcom.com wrote: > > Hi, > > Are there any considerations for using POST with SSL? My code includes > the following commands: > > HTSSL_protMethod_set(HTSSL_V23); > HTSSL_verifyDepth_set(2); > HTSSLhttps_init(YES); > > I have SSL working with Basic authentication using a GET, but with a POST, > the request hangs. The the last few lines ofoutput with Trace set to > "sop" is: > > SSL_connect: SSLv3 read server certificate A > SSL_connect: SSLv3 read server key exchange A > SSL_connect: SSLv3 read server done A > SSL_connect: SSLv3 write client key exchange A > SSL_connect: SSLv3 write change cipher spec A > SSL_connect: SSLv3 write finished A > SSL_connect: SSLv3 flush data > SSL_connect: SSLv3 read finished A > HTSSLWriter. SSL returned 0 > HTSSLWriter. 336 bytes written to 3 > Uploading... Holding 0x101439a0 for 2000 ms using time 0x10160f28 > HTSSL New... Found SSL 0x10164240 with sd = 3 > HTSSL....... New reference count = 2 > HTSSLReader. SSL returned 0 > HTSSLReader. 25 bytes read from socket 3 > Host info... New mode is 1 for host 0x101446d0 > Net Manager. 1 active sockets, increasing persistent sockets to 1 > Host info... added host 0x101446d0 as persistent > Net Object.. Persistent connection set ON succeeded > StreamStack. Constructing stream stack for message/x-rfc822-cont to > www/debug > Host........ passing 23 bytes as consumed to 0x10145b80 > Host........ 2 bytes remaining > Host........ passing 2 bytes as consumed to 0x10145b80 > Host........ 0 bytes remaining > MIME........ FREEING.... > HTSSLReader. CONTINUE > HTTP........ Continuing > > > Any help would be appreciated. > > Thanks! > > Erik. > >
Received on Wednesday, 1 October 2003 16:28:57 UTC