Thanks. The problem is SSL_Read hangs there without giving any error. The sequence should be:
HTTP/1.1 100 Continue
Server: Microsoft-IIS/5.0
Date: Thu, .....
HTTP/1.1 200 OK
......
But after the Date header and empty line, SSL_read() just hangs there. If there is error returns, then I can handle it. It hangs there, I can't do anything?
Any ideas? Is it a bug in SSL_Read? Between Date header and HTTP/1.1 200 OK, the
terminators 0d 0a 0d 0a confused SSL_read?
From: "Gait Boxman" </groups?hl=en&lr=&ie=UTF-8&q=author:gait.boxman%40tie.nl+> ([EMAIL PROTECTED] <mailto:gait.boxman%40tie.nl>) Subject: Re: SSL_read() hang after read http 100 continue headers
View this article only </groups?hl=en&lr=&ie=UTF-8&selm=aps55l%241kgg%241%40FreeBSD.csie.NCTU.edu.tw>
Newsgroups: mailing.openssl.users </groups?hl=en&lr=&ie=UTF-8&group=mailing.openssl.users> Date: 2002-10-31 12:56:02 PST
This is a multi-part message in MIME format.
------=_NextPart_000_0084_01C28127.AC547900
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Looks like your code is impatient.=20
When you get continue, 4 retries won't be enough to get the next =
response.
Basically, if you get an SSL_ERROR_WANT_READ, you just need to keep =
continuing to retry the SSL_read, if you expect more data that is. So, =
if you expect a server response, keep trying till you get some (you may =
want to hack in a timeout there), then process the response. If it's a =
continue, discard it and just start again reading till you get some...
