Hello!
I'm stuck to understand how nginx handles encrypting messages with TLS protocol, when sendfile is ON.
The premise of sendfile is not to use user space, just redirect given file straight to the socket. So, it seems that there is no way to encrypt the file in the user space, using sendfile alone.
Is Nginx using some other solution, as described by folks from netflix? ( https://people.freebsd.org/~rrs/asiabsd_2015_tls.pdf ), or sendfile is always off, in HTTPS communication?
I'm stuck to understand how nginx handles encrypting messages with TLS protocol, when sendfile is ON.
The premise of sendfile is not to use user space, just redirect given file straight to the socket. So, it seems that there is no way to encrypt the file in the user space, using sendfile alone.
Is Nginx using some other solution, as described by folks from netflix? ( https://people.freebsd.org/~rrs/asiabsd_2015_tls.pdf ), or sendfile is always off, in HTTPS communication?