<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 8/13/2018 11:25 AM, Viktor Dukhovni
wrote:
</div>
<blockquote type="cite"
cite="mid:EC677062-1605-4764-BA48-A683FF177D67@dukhovni.org">
<blockquote type="cite">
<pre wrap="">On Aug 13, 2018, at 2:13 PM, Jordan Brown <a class="moz-txt-link-rfc2396E" href="mailto:openssl@jordan.maileater.net"><openssl@jordan.maileater.net></a> wrote:
I'm curious: how did this ever work for HTTPS, where for a POST request you have to see the end of the request body before you can (in general) send the response?
</pre>
</blockquote>
<pre wrap="">
This is no longer OpenSSL-specific. Best to wind down this thread.
HTTP has a "Content-Length:" header or alternatively supports Chunked
transfers.</pre>
</blockquote>
<br>
You're right that it's not OpenSSL-specific, but the general topic
of "how do you design protocols atop TLS" and "how do you take a TCP
protocol and put it on top of TLS" seem relevant.<br>
<br>
Huh. Looking closely, I see that HTTP requires header-based framing
information when the request has a body - either Content-Length or
Transfer-Encoding. And here I thought I had a pretty decent
understanding of basic HTTP. Maybe I've just never hand-crafted a
POST request. I learn something new every day.<br>
<pre class="moz-signature" cols="72">--
Jordan Brown, Oracle Solaris</pre>
</body>
</html>