Lukas Tribus Wrote: ------------------------------------------------------- > > 4 threads and 4 CPU (both for apache and nginx) with 100% CPU load > on test > > So, what's the answer now about the http/https (4600/550) ratio for > the > > specific case I presented? > > It should perform the same as Apache in this case. Well, as I said earlier, with Apacby adrhc - Nginx Mailing List - English
Lukas Tribus Wrote: ------------------------------------------------------- > That depends: how many nginx workers do you have compared to > how many apache threads and how does your per-core CPU load > look like when benchmarking? > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginxby adrhc - Nginx Mailing List - English
Lukas Tribus Wrote: ------------------------------------------------------- > > I'll do it but I guess the test will no longer be so relevant > because I want > > to simulate different users. > > Real user/browser DO keep-alive. ... I agree but I think that separate/different simultaneous users won't use a common connection so for this very specific scenario keep-alby adrhc - Nginx Mailing List - English
I'm just a bit surprised that "port_in_redirect off" does not also work. But that's ok -- I'm often surprised. There's a "if" in src/http/ngx_http_header_filter_module.c which changes port's value from 443 to 0 when on ssl + port initially 443 so https://adrhc.go.ro/ffp_0.7_armv5 would redirect to http when port_in_redirect is off. "... but I don't know what is the seby adrhc - Nginx Mailing List - English
Hi, here's some clarifications: What is the thing writing to nginx? (stunnel, I think) stunnel according to the setup: Transmission remote GUI:443 -> sshttp:443 -> stunnel:1443 -> nginx:127.0.0.1:443 (no ssl, with listen ... proxy_protocol, port_in_redirect on) How is it configured? accept = 192.168.1.31:1443 connect = 127.0.0.1:1081 protocol = proxy sni = tls:tti.go.ro cby adrhc - Nginx Mailing List - English
Hi, the log come from nginx error log. I simply start the Transmission remote GUI and I get only this in error log: 2016/09/21 10:32:13 3909#0: *327 broken header: "> : X,u \kc ; J=ޛXfoVr_<