Awesome.. I can confirm that this works.. thanks -bhaktaby bhaktaonline - Nginx Mailing List - English
Thanks for the quick response, Sergey, I set: postpone_output 200; killed/restarted the server this should have postponed writing output until 200 bytes is available. The HTTP header is 244 bytes and it should have triggered an output.. I however still see on single TLS record which has both header and data: Any suggestions? Logs: 2018/12/26 16:59:00 14290#0: *1 content phaby bhaktaonline - Nginx Mailing List - English
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 13248#0: *1 SSL buf copy: 244 2018/12/26 14:10:34 13248#0: *1 SSL buf copy: 16140 2018/12/26 14:10:34 13248#0: *1 SSL to write: 16384 <snip> While the header getsby bhaktaonline - Nginx Mailing List - English