Difference between revisions of "Fastcgi read timeout"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
* [[Track HTTP Application Response time in Nginx]]: <code>[[upstream_response_time]]</code> | * [[Track HTTP Application Response time in Nginx]]: <code>[[upstream_response_time]]</code> | ||
* <code>[[504 Gateway Time-out]]</code> | * <code>[[504 Gateway Time-out]]</code> | ||
| + | * [[/wiki/Special:RecentChanges]] | ||
== See also == | == See also == | ||
Latest revision as of 16:07, 27 September 2024
Syntax: fastcgi_read_timeout time; Default: fastcgi_read_timeout 60s; Context: http, server, location
Defines a timeout for reading a response from the FastCGI server. The timeout is set only between two successive read operations, not for the transmission of the whole response. If the FastCGI server does not transmit anything within this time, the connection is closed.
Related[edit]
- PHP
/etc/nginx/nginx.conf/var/log/nginx/access.log | awk '{print $(NF-1)}'- Track HTTP Application Response time in Nginx:
upstream_response_time 504 Gateway Time-out- /wiki/Special:RecentChanges
See also[edit]
- Web server: Nginx:
/etc/nginx/nginx.conf,nginx -t, Nginx logs, Nginx change log, PHP,php-fpm, Let's encrypt, Nginx directives, Reverse Proxy, Configure HTTP redirection Nginx, Return,proxy_pass (Reverse proxy),ngx_http_rewrite_module,/etc/nginx/sites-enabled/,error.log,access.log,/nginx status, AIO
Advertising:
