Re: buffering / uploading large files

On Tuesday 10 February 2015 23:13:49 nginxuser100 wrote: > Hi Kurt, where can I get a patch for nginx version 1.6.2 (the 'official' > stable version as of today)? Thank you! > Why not to use the latest mainline version? See the difference: http://nginx.com/blog/nginx-1-6-1-7-released/ wbr, Va

Re: buffering / uploading large files

Hi Kurt, where can I get a patch for nginx version 1.6.2 (the 'official' stable version as of today)? Thank you! Posted at Nginx Forum: http://forum.nginx.org/read.php?2,256378,256563#msg-256563 ___ nginx mailing list nginx@nginx.org http://mailman.ngi

Re: Google dumps SPDY in favour of HTTP/2, any plans for nginx?

Pedantic, but I object to the wording in the title :) ... SPDY was/is an experimental branch of HTTP/2, and now that HTTP/2 is in the final stages of becoming a standard, there is no longer the need for SPDY and hence the announcement of a deprecation timeline -- it's not and never was SPDY vs. HTT

Google dumps SPDY in favour of HTTP/2, any plans for nginx?

Google dumps SPDY in favour of HTTP/2, any plans ore roadmap for HTTP/2 in nginx? see https://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-http-is_9.html "HTTP is the fundamental networking protocol that powers the web. The majority of sites use version 1.1 of HTTP, which was defined in 19

Re: [nginx-announce] nginx-1.7.10

Hello Nginx users, Now available: Nginx 1.7.10 for Windows http://goo.gl/tzDzKY (32-bit and 64-bit versions) These versions are to support legacy users who are already using Cygwin based builds of Nginx. Officially supported native Windows binaries are at nginx.org. Announcements are also availa

nginx-1.7.10

Changes with nginx 1.7.1010 Feb 2015 *) Feature: the "use_temp_path" parameter of the "proxy_cache_path", "fastcgi_cache_path", "scgi_cache_path", and "uwsgi_cache_path" directives. *) Feature: the $upstream_header_time variable.

Re: catching 408 response from upstream server

Hi, On 02/10/2015 08:35 AM, shmulik wrote: Hi, I'm using nginx as reversed proxy, using the proxy module. Whenever i get a response code >= 400 from the upstream server, i'm redirecting the client to a different url. This is the configuration i use (simplified): location ~ "^/proxy/hos

Re: G-WAN assumptions: Part of truth/lies?

On 08 Feb 2015, at 02:39, B.R. wrote: > - Is their nginx configuration suitable for valid benchmark results? Probably you should disable "accept_mutex off": http://nginx.org/en/docs/ngx_core_module.html#accept_mutex Because the mutex in combination with "multi_accept on”: http://nginx.org/en/d

Re: catching 408 response from upstream server

I do not see anything in error_page documentation stating it would not send anything for 408. I suggest a problem on your side. Do you have HTTP Requests/Responses traces to show? Any sign of trouble (configuration, not applied,

Re: Benchmarking with wrk

> On 08 Feb 2015, at 04:51, B.R. wrote: > > Hello, > > I am starting to play with some benchmarking tools. > Following Konstantin advice (video from the last user conference ;o) ), I am > avoiding ab. > > After a few runs, I notice I get some 'Socket errors' of diffent types: > connect and t