Yes it's resolved.
I've change the cache path yesterday and a few minutes ago, I noticed that
error message:
"2016/03/19 12:31:02 [emerg] 8984#8984: cache "my_zone" uses the
"/tmp/nginx/dev" cache path while previously it used the "/tmp/nginx" cache
path"
It seems it was enough to prevent the ca
Although you stated you problem was resolved, you need to understand what
you are configuring/testing.
In the first message you posted, the first response URL using the cache
(starting with '/kuriyamacache') did not correspond to the alleged request
headers' URL ('thumbnail_0' vs 'thumbnail_1'), s
Great! =) Make sure proxy buffering stays on - that will bypass the cache
if turned off, and make sure your key space is large because you'll throw
500s for everything if it runs out (I figured it would evict a key if it
ran out of space, and what was a wrong assumption)
On Sat, Mar 19, 2016 at 4
Seems like it's resolved:
$ curl -I
http://dev.ts-export.com/kuriyamacache/images/parts/13375/thumbnail_0/1_1.jpg
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 19 Mar 2016 20:42:46 GMT
Content-Type: image/jpeg
Content-Length: 53491
Connection: keep-alive
Last-Modified: Thu, 10 Mar 2016 05:01:30 GMT
I think I've run into the problem before - move the proxypass statement
from the top of the location stanza to the bottom, and I think that will
solve your issue.
On Sat, Mar 19, 2016 at 4:10 PM, shiz wrote:
> Been playing with this for 2 days.
>
> proxy_pass is working correctly but the proxy_
Been playing with this for 2 days.
proxy_pass is working correctly but the proxy_cache_path remains empty
whatever I make.
Here's the source I use for tests:
root@NC-PH-0657-10:/etc/nginx/snippets# curl -X GET -I
http://www.kuriyama-truck.com/images/parts/13375/thumbnail_0/1_1.jpg
HTTP/1.1 200 O
Hello!
George Wrote:
---
> But no love for LibreSSL users as Nginx 1.9.12 seems to broken
> compilation against LibreSSL 2.2.6 for me
> https://trac.nginx.org/nginx/ticket/908#ticket ?
Great news, there's a fix in LibreSSL:
http
Hello,
Thanks for this new nginx release!
It would be great to officially support LibreSSL in nginx. Until now, nginx
had no problem compiling LibreSSL using "--with-openssl=".
Best Regards
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,264770,264805#msg-264805
thanks I switched back to OpenSSL for now :)
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,264770,264794#msg-264794
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
But sir I'm wine chips.
On 24-Feb-2016 10:41 pm, "Maxim Dounin" wrote:
> Hello!
>
> On Wed, Feb 24, 2016 at 11:57:37AM -0500, George wrote:
>
> > Thanks Maxim and Nginx !
> >
> > But no love for LibreSSL users as Nginx 1.9.12 seems to broken
&g
Hello!
On Wed, Feb 24, 2016 at 11:57:37AM -0500, George wrote:
> Thanks Maxim and Nginx !
>
> But no love for LibreSSL users as Nginx 1.9.12 seems to broken compilation
> against LibreSSL 2.2.6 for me https://trac.nginx.org/nginx/ticket/908#ticket
> ?
It's not expected t
Thanks Maxim and Nginx !
But no love for LibreSSL users as Nginx 1.9.12 seems to broken compilation
against LibreSSL 2.2.6 for me https://trac.nginx.org/nginx/ticket/908#ticket
?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,264770,264780#msg-264780
Hello Nginx users,
Now available: Nginx 1.9.12 for Windows
https://kevinworthington.com/nginxwin1912 (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
Changes with nginx 1.9.1224 Feb 2016
*) Feature: Huffman encoding of response headers in HTTP/2.
Thanks to Vlad Krasnov.
*) Feature: the "worker_cpu_affinity" directive now supports more than
64 CPUs.
*) Bugfix: com
14 matches
Mail list logo
