RFC 2616 describes HTTP/1.1, which is probably more than he needs. HTTP/1.1 is significantly more work to implement than 1.0 (it requires supporting the chunked transfer-encoding, for example). HTTP/1.0 (RFC 1945) is often a better choice for little HTTP-based applications.
It wasn't clear to me whether Scott was looking for HTTP protocol information, though, or OpenSSL API help. Scott? Michael Wojcik Principal Software Systems Developer, Micro Focus Department of English, Miami University > -----Original Message----- > From: Neff Robert A [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 10, 2002 8:20 AM > To: '[EMAIL PROTECTED]'; 'Scott Frazor' > Subject: RE: HTTPS Post > > > Scott, > Read http://www.ietf.org/rfc/rfc2616 for HTTP information > > -----Original Message----- > From: Scott Frazor [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 09, 2002 6:00 PM > To: [EMAIL PROTECTED] > Subject: HTTPS Post > > > Can anyone give me a rough idea on how to prepare and send a > https POST via openssl? I know how to open a socket and connect > SSL, but I'm missing something when it comes to sending a HTTPS > POST and RECEIVING the response. > I'm not sure if I'm asking the question right. Any ideas? > > Thanks, > Scott ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
