ngx_http_upstream_test_next u->peer.tries > 1

2017-11-24 Thread crasyangel
assume all servers always fail in upstream nginx would call ngx_http_upstream_next when u->peer.tries > 1, and call ngx_http_upstream_finalize_request directly when u->peer.tries == 1 it would not pass NGX_PEER_FAILED to u->peer.free so how peer->fails increase when last retry fail? Posted at

How nginx write same log file concurrently

2017-03-29 Thread crasyangel
Write same fd after fork() directly, it would do the work? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,273286,273286#msg-273286 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

log status actually not real status

2016-08-31 Thread crasyangel
Nginx would log status to 200 after response header had sent when upstream prematurely closed connection I think nginx should log status to 502, even though client recv 200 static u_char * ngx_http_log_status(ngx_http_request_t *r, u_char *buf, ngx_http_log_op_t *op) { ngx_uint_t status;

Re: internal location keepalive_requests issue

2016-08-26 Thread crasyangel
if (r->keepalive) { if (clcf->keepalive_timeout == 0) { r->keepalive = 0; } else if (r->connection->requests >= clcf->keepalive_requests) { r->keepalive = 0; } else if (r->headers_in.msie6 && r->method == NGX_HTTP_POST

internal location keepalive_requests issue

2016-08-26 Thread crasyangel
location /hls { error_page 404 = @hls; keepalive_requests 1000; } location @hls { # Serve HLS fragments types { application/vnd.apple.mpegurl m3u8; video/mp2t ts; } root /tmp;

Would nginx use multi block device instead of file system

2016-07-29 Thread crasyangel
use block device directly like ats and squid, and build request offset hash table, should be more effectively? Would nginx support this? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,268627,268627#msg-268627 ___ nginx mailing list nginx@ng

Re: nginx not forwarding requests to backend servers.

2016-07-27 Thread crasyangel
u.default_port = 80; in ngx_http_upstream_server add a new upstream upstream ssl_myappliationsite.net { ip_hash; server backendappsite1.net:443; server backendappsite2.net:443; server backendappsite3.net:443; } server { listen 443 ssl; server_name myapplicationsite.net; keepalive_timeout 70; s

Re: nginx not forwarding requests to backend servers.

2016-07-27 Thread crasyangel
don't get it. proxy_set_header host? upstream name only for lookup upstream, it has no business with any proxy headers Posted at Nginx Forum: https://forum.nginx.org/read.php?2,268548,268552#msg-268552 ___ nginx mailing list nginx@nginx.org http://ma

Re: nginx not forwarding requests to backend servers.

2016-07-27 Thread crasyangel
test ok with nginx 1.8.0，which nginx version you use? nginx must be confused by same domain name and upstream name, rename the upstream name! Posted at Nginx Forum: https://forum.nginx.org/read.php?2,268548,268550#msg-268550 ___ nginx mailing list ngin

Re: epoll_wait() reported that client prematurely closed connection, so upstream connection is closed too while sending request to upstream

2016-07-27 Thread crasyangel
I guess the response header has wrong with chrome, post the entire response header, and check again Posted at Nginx Forum: https://forum.nginx.org/read.php?2,258050,268539#msg-268539 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailm

Re: proxy_next_upstream http_404?

2016-07-27 Thread crasyangel
show your upstream and proxy full config Posted at Nginx Forum: https://forum.nginx.org/read.php?2,268529,268537#msg-268537 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx