12:37 21-6-2014 nginx 1.7.3.1 RedKnight
Based on nginx 1.7.3 (20-6-2014) with;
+ new best practice ssl_ciphers example (nginx-win.conf)
+ fastcgi/upstream fix:
http://forum.nginx.org/read.php?29,250947,251007#msg-251007
+ form-input-nginx-module
(https://github.com/calio/form-input-nginx-module)
+
Nevermind, I see there are multiple such cases, so I guess it's by design
that you don't catch the error at the parsing stage.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,250869,251093#msg-251093
___
nginx mailing list
nginx@nginx.org
http
I see your point.
By the way, is there a more appropriate forum or email list I should use for
these kinds of questions?
I'm a fairly fresh computer science student who just started working in the
industry, and all I'm ever allowed to work on, is Java and C#,
so I decided to do some C hacking on a
Hi,
> @Lukas, we're using nginx-1.6 and byte range caching is already enabled
> by default(i guess). Below is the curl request :-
>
> curl -H Range:bytes=16- -I
> http://videos.files.com/files/videos/2014/06/20/14032606291de19-360.mp4
> HTTP/1.1 206 Partial Content
> Server: nginx
> D