| http://sha256timestamp.ws.symantec.com/sha256/timestamp | |
| http://timestamp.globalsign.com/scripts/timstamp.dll | |
| https://timestamp.geotrust.com/tsa | |
| http://timestamp.verisign.com/scripts/timstamp.dll | |
| http://timestamp.comodoca.com/rfc3161 | |
| http://timestamp.wosign.com | |
| http://tsa.startssl.com/rfc3161 | |
| http://time.certum.pl | |
| http://timestamp.digicert.com | |
| https://freetsa.org |
By default when Nginx starts receiving a response from a FastCGI backend (such as PHP-FPM) it will buffer the response in memory before delivering it to the client. Any response larger than the set buffer size is saved to a temporary file on disk.
This process is outlined at the Nginx ngx_http_fastcgi_module page manual page.