NGINX TLS Behavior

Sergey Kandaurov pluknet at nginx.com
Wed Dec 26 10:41:45 UTC 2018


> On 26 Dec 2018, at 13:17, bhaktaonline <nginx-forum at forum.nginx.org> wrote:
> 
> Hello,
> 
> 
> I have a question on NGINX's behavior during TLS.
> 
> I see that NGINX combines HTTP header and Data together into a SSL record. 
> You can see from the logs below that 
> 
> <snip>
> 
> 2018/12/26 14:10:34 [debug] 13248#0: *1 SSL buf copy: 244
> 2018/12/26 14:10:34 [debug] 13248#0: *1 SSL buf copy: 16140
> 2018/12/26 14:10:34 [debug] 13248#0: *1 SSL to write: 16384
> 
> <snip>
> 
> 
> While the header gets generated earlier, its written to along with data. Is
> there a way (i mean a configurable way) to tell NGINX to write just the
> headers, so that header goes out in a single TLS record?

Yes, there's a way to send headers separately.
See http://nginx.org/r/postpone_output for details.

-- 
Sergey Kandaurov



More information about the nginx mailing list