| commit | f4e1357df5fd219083c9c26c319f7ceff1677378 | |
| author | Glenn Strauss <gstrauss@gluelogic.com> | |
| Sun, 10 Sep 2017 22:45:39 +0000 (10 18:45 -0400) | ||
| committer | Glenn Strauss <gstrauss@gluelogic.com> | |
| Sun, 10 Sep 2017 22:52:41 +0000 (10 18:52 -0400) | ||
| tree | 7742e398210c10c7f7ae021c4817d1072fc9f6f9 | treesnapshot (tar.gz zip) |
| parent | 3622d2b66a5a0cb18b6b16c2284d79ede82debf6 | commitdiff |
[mod_openssl] ssl.read-ahead="disable" for stream
set default ssl.read-ahead = "disable" for streaming when
server.stream-request-body = 1 or 2 is set in the global scope
It is still recommended that embedded and other low-memory systems
explicitly set ssl.read-ahead = "disable" in the global scope
(regardless of server.stream-request-body setting)
On the other hand, for systems which enable server.stream-request-body
to non-zero value, and for which sufficient memory is available, then
ssl.read-ahead = "enable" is recommended and should be explicitly set
in the global or $SERVER["socket"] configuration blocks in lighttpd.conf
x-ref:
"https POST requests buffered in RAM since v1.4.41?"
https://redmine.lighttpd.net/boards/2/topics/7520
set default ssl.read-ahead = "disable" for streaming when
server.stream-request-body = 1 or 2 is set in the global scope
It is still recommended that embedded and other low-memory systems
explicitly set ssl.read-ahead = "disable" in the global scope
(regardless of server.stream-request-body setting)
On the other hand, for systems which enable server.stream-request-body
to non-zero value, and for which sufficient memory is available, then
ssl.read-ahead = "enable" is recommended and should be explicitly set
in the global or $SERVER["socket"] configuration blocks in lighttpd.conf
x-ref:
"https POST requests buffered in RAM since v1.4.41?"
https://redmine.lighttpd.net/boards/2/topics/7520
| src/mod_openssl.c | diffblobblamehistory |