On Thu, Apr 19, 2007 at 11:46:49PM +0200, Aleksandar Lazic wrote:
On Don 19.04.2007 22:20, Igor Sysoev wrote:
Changes with nginx 0.5.18 19 Apr
2007
*) Feature: the ngx_http_sub_filter_module.
Is this like a content filter at post-filter-after-all-other-modules?
Is this like a content filter at pre-send-to-client state?
The current filter chain is
V
ranges
V
addition
V
sub
V
ssi
V
charset
V
gzip
V
chunks
V
client
*) Feature: the "$upstream_http_..." variables.
*) Feature: now the $upstream_status and $upstream_response_time
variables keep data about all upstreams before X-Accel-Redirect.
Can this variables used to be logged like this?
e.g.:
log_format timing '$remote_addr - $remote_user [$time_local] $request '
'upstream_response_time $upstream_response_time';
log_format up_head '$remote_addr - $remote_user [$time_local] $request '
'upstream_http_content-type $upstream_http_content-type';
If yes coool ;-)
The primary use of $upstream_status and $upstream_response_time is logging.
Note
-$upstream_http_content-type
+$upstream_http_content_type
6 messages in ru.sysoev.nginxRe: nginx-0.5.18
