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?by crasyangel - Nginx Mailing List - English
Write same fd after fork() directly, it would do the work?by crasyangel - Nginx Mailing List - English
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; if (r->err_status) { status = r->err_status; } else if (r->headers_by crasyangel - Nginx Mailing List - English
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; add_header Cache-Control no-cache; keepalive_requests 1000; } keepalive_requests must be large enough in this two location meanwhile if set keepalive_requests to 0 or 1 in /hls, keepalive_requests would notby crasyangel - Nginx Development
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 && (clcf->keepalive_disableby crasyangel - Nginx Mailing List - English
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; add_header Cache-Control no-cache; keepalive_requests 1000;by crasyangel - Nginx Mailing List - English
use block device directly like ats and squid, and build request offset hash table, should be more effectively? Would nginx support this?by crasyangel - Nginx Mailing List - English
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; ssl_certificate /appssl/fd.crt; ssl_certificate_key /appssl/lb.key; ssl_protocols Tby crasyangel - Nginx Mailing List - English
don't get it. proxy_set_header host? upstream name only for lookup upstream, it has no business with any proxy headersby crasyangel - Nginx Mailing List - English
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!by crasyangel - Nginx Mailing List - English
Do have any plan for tcp splicing?_______________________________________________ nginx-devel mailing list nginx-devel@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx-develby crasyangel - Nginx Development
Do have any plan for tcp splicing?_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginxby crasyangel - Nginx Mailing List - English
I guess the response header has wrong with chrome, post the entire response header, and check againby crasyangel - Nginx Mailing List - English
show your upstream and proxy full configby crasyangel - Nginx Mailing List - English