Hi, Upon further testing, it appears the problem exists even with proxy_cache'd
files with "proxy_cache_lock on".
(Please consider this a serious bug, which I'm surprised hasn't been detected
before; verified on recently released 1.7.2)
On Jun 24, 2014, at 8:58 PM, Paul Schlie wrote:
> Again
Again thank you. However ... (below)
On Jun 24, 2014, at 8:30 PM, Maxim Dounin wrote:
> Hello!
>
> On Tue, Jun 24, 2014 at 07:51:04PM -0400, Paul Schlie wrote:
>
>> Thank you; however it appears to have no effect on reverse proxy_store'd
>> static files?
>
> Yes, it's part of the cache machi
Hello!
On Tue, Jun 24, 2014 at 08:18:04PM -0400, badtzhou wrote:
> We are trying to use resolver on upstream. It is not working for some
> reason. We are using nginx 1.6.0. Supposedly the feature should be available
> on 1.5.12.
>
> When we try to use it, It always give us an error. nginx: [emer
Hello!
On Tue, Jun 24, 2014 at 07:51:04PM -0400, Paul Schlie wrote:
> Thank you; however it appears to have no effect on reverse proxy_store'd
> static files?
Yes, it's part of the cache machinery. The proxy_store
functionality is dumb and just provides a way to store responses
received, not
We are trying to use resolver on upstream. It is not working for some
reason. We are using nginx 1.6.0. Supposedly the feature should be available
on 1.5.12.
When we try to use it, It always give us an error. nginx: [emerg] invalid
parameter "resolve" in... And when I checked the source code, it d
Thank you; however it appears to have no effect on reverse proxy_store'd static
files?
(Which seems odd, if it actually works for cached files; as both are first read
into temp_files, being the root of the problem.)
Any idea on how to prevent multiple redundant streams and corresponding
temp_f
Hello!
On Tue, Jun 24, 2014 at 02:49:57PM -0400, Paul Schlie wrote:
> I've noticed that multiple (as great as 8 or more) parallel
> redundant streams and corresponding temp_files are opened
> reading the same file from a reverse proxy backend into nginx,
> upon even a single request by an up-s
I've noticed that multiple (as great as 8 or more) parallel redundant streams
and corresponding temp_files are opened reading the same file from a reverse
proxy backend into nginx, upon even a single request by an up-stream client, if
not already cached (or stored in a static proxy'ed file) loca
Hallo Maxim,
thanks. I copy some errorpages in the custom errorpage folder and all is OK.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251118,251134#msg-251134
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinf
Hello!
On Tue, Jun 24, 2014 at 06:38:59AM -0400, TheBritishGeek wrote:
> I have tried
>
> if ($remote_addr ~ "^(1.1.1.1|a:b:c:d::1:2)$")
> {
> proxy_cache_bypass $http_secret_header;
> }
>
> But is does not pass testing
>
> nginx: [emerg] "proxy_cache_bypas
I found the issue(s). I am not sure why the error log did not have any logs
after the lua thread got launched.
Here is the updated /etc/nginx/nginx.conf
location / {
set $dbKey "";
content_by_lua '
local a = ngx.var.http_cookie
loca
I have tried
if ($remote_addr ~ "^(1.1.1.1|a:b:c:d::1:2)$")
{
proxy_cache_bypass $http_secret_header;
}
But is does not pass testing
nginx: [emerg] "proxy_cache_bypass" directive is not allowed here
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,2
My nginx.conf
upstream testdb {
postgres_server 10.0.9.43:9000 dbname=testdb user=postgres
password=postgres;
postgres_keepalive max=100 mode=multi overflow=ignore;
}
location / {
set $x "";
content_by_lua '
local a = ngx.v
13 matches
Mail list logo
