comparison src/imap/ngx_imap_core_module.c @ 212:56688ed172c8 NGINX_0_3_53

nginx 0.3.53 *) Change: the "add_header" directive adds the string to 204, 301, and 302 responses. *) Feature: the "server" directive in the "upstream" context supports the "weight" parameter. *) Feature: the "server_name" directive supports the "*" wildcard. *) Feature: nginx supports the request body size more than 2G. *) Bugfix: if a client was successfully authorized using "satisfy_any on", then anyway the message "access forbidden by rule" was written in the log. *) Bugfix: the "PUT" method may erroneously not create a file and return the 409 code. *) Bugfix: if the IMAP/POP3 backend returned an error, then nginx continued proxying anyway.
author Igor Sysoev <http://sysoev.ru>
date Fri, 07 Jul 2006 00:00:00 +0400
parents 3689cd4e3228
children fbf2b2f66c9f
comparison
equal deleted inserted replaced
211:f04a54878110 212:56688ed172c8
203 203
204 ngx_conf_merge_size_value(conf->imap_client_buffer_size, 204 ngx_conf_merge_size_value(conf->imap_client_buffer_size,
205 prev->imap_client_buffer_size, 205 prev->imap_client_buffer_size,
206 (size_t) ngx_pagesize); 206 (size_t) ngx_pagesize);
207 ngx_conf_merge_msec_value(conf->timeout, prev->timeout, 60000); 207 ngx_conf_merge_msec_value(conf->timeout, prev->timeout, 60000);
208 ngx_conf_merge_unsigned_value(conf->protocol, prev->protocol, 208 ngx_conf_merge_uint_value(conf->protocol, prev->protocol,
209 NGX_IMAP_IMAP_PROTOCOL); 209 NGX_IMAP_IMAP_PROTOCOL);
210 ngx_conf_merge_value(conf->so_keepalive, prev->so_keepalive, 0); 210 ngx_conf_merge_value(conf->so_keepalive, prev->so_keepalive, 0);
211 211
212 212
213 if (conf->pop3_capabilities.nelts == 0) { 213 if (conf->pop3_capabilities.nelts == 0) {