undefined symbol: ldap_init_fd

I successfully compile Nginx with Nginx-auth-ldap and when I start Nginx , the worker process turn defunct and I see - nginx: worker process: symbol lookup error: nginx: worker process: undefined symbol: ldap_init_fd in the error logs without able to utilize ldap, what could be wrong here? Tha

Re: Using variables on nginx.

Ok thx, I test it and really doesnt work. :) 2014-04-11 14:16 GMT-05:00 Valentin V. Bartenev : > On Friday 11 April 2014 13:58:44 Raul Hugo wrote: > > I can Use variables to define IP:Port on upstreams directive? > > > > For example: > > > > upstream cluster-servers { > >$server01;

Re: Using variables on nginx.

On Friday 11 April 2014 13:58:44 Raul Hugo wrote: > I can Use variables to define IP:Port on upstreams directive? > > For example: > > upstream cluster-servers { >$server01; >$server02; > } > No, you can't. Please also note: http://nginx.org/en/docs/faq/variables_in_co

Using variables on nginx.

I can Use variables to define IP:Port on upstreams directive? For example: upstream cluster-servers { $server01; $server02; } -- Un abrazo! *Raúl Hugo * *Miembro Asociadohttp://apesol.org.pe SysAdmin Cel. #961-710-

Re: Case insensitive location

Oh my, what an idiot i've been. Thank you very much for your post! I moved it up above my cache and it works just fine, here is what i've been able to shorten it down to now: location ~* /card/ { rewrite (?i)^/card/([a-zA-Z0-9_+]+)/(.*).png$ /card.php?name=$2&type=$1;

Re: Requests being blocked client-side

Hello! On Fri, Apr 11, 2014 at 12:45:17PM -0400, justink101 wrote: > I am seeing super strange behavior and I am absolutely stumped. If I open up > two tabs in Google Chrome (34), and in the first refresh our application > (foo.ourapp.com), which makes an ajax requests (via jQuery) that takes 20

Requests being blocked client-side

I am seeing super strange behavior and I am absolutely stumped. If I open up two tabs in Google Chrome (34), and in the first refresh our application (foo.ourapp.com), which makes an ajax requests (via jQuery) that takes 20 or so seconds to complete. Then in the other new tab hit refresh on (foo.ou

Re: OpenSSL leaks server-Keys / The Heartbleed Bug

Am 11.04.2014 18:34 schrieb Jim Ohlstein: Thanks for the link. On a quick read it seems their conclusion is that while it is *extremely* unlikely that your private key(s) was/were stolen using nginx, you should still re-key and revoke. While comforting, not really of any great practical help. A

Re: OpenSSL leaks server-Keys / The Heartbleed Bug

Hello, On 4/11/14, 12:11 PM, Valentin V. Bartenev wrote: "Answering the Critical Question: Can You Get Private SSL Keys Using Heartbleed?" @ http://blog.cloudflare.com/answering-the-critical-question-can-you-get-private-ssl-keys-using-heartbleed Thanks for the link. On a quick read it seems

Re: OpenSSL leaks server-Keys / The Heartbleed Bug

"Answering the Critical Question: Can You Get Private SSL Keys Using Heartbleed?" @ http://blog.cloudflare.com/answering-the-critical-question-can-you-get-private-ssl-keys-using-heartbleed wbr, Valentin V. Bartenev ___ nginx mailing list nginx@nginx

Re: Case insensitive location

On Friday 11 April 2014 07:59:42 Callumpy wrote: > I'm still having no luck with it. > > As I said before, when I use location ~* ^/card/, it just 404s all the time > unless I disable my cache. > > Here is my cache code, I have no idea why it does this. > > # Cache setup. > location ~*

Re: Case insensitive location

do you have tryfiles enabled? i'd try this to check, if the request reaches the nright location-block location ^~ /card/ { ... access_log /var/log/nginx/cards.log combined; ... } if so, your must look inside your locatiuon, if not, somwhere else regar

Re: Case insensitive location

I'm still having no luck with it. As I said before, when I use location ~* ^/card/, it just 404s all the time unless I disable my cache. Here is my cache code, I have no idea why it does this. # Cache setup. location ~* \.(jpg|jpeg|png|gif|ico|css|xml|js|woff)$ { expires