Am 11.09.2014 00:56 schrieb Michal Cichra:
What I propose is a configuration flag, to set
`SSL_CTX_set_default_verify_paths`.
Careful what you wish for..
I didnt check the surrounding code, but above call and CAfile/CApath
sets (if cmd-line or via API wont matter)
has "funny" error condition
Hi,
first I would like to thank for the proxy ssl verification that landed in nginx
1.7.
Regarding that, there is one slight problem I’ve found, when creating a proxy,
that dynamically accesses different hosts.
The configuration is limited to setting a certificate and does not use CA path
at a
Maxim Dounin Wrote:
> nginx needs a client request to be able to request a
> resource from a backend and to save it to the cache.
I'm afraid my explanation wasn't clear enough.
There's no need to make nginx able to make requests to fastcgi on it's own
initiative.
How it works today:
A client mak
You start a process in userland then kill that userland.
No surprises there...
Consider running nginx as a service/unconnected to your user session.
---
*B. R.*
On Wed, Sep 10, 2014 at 6:16 PM, ronlemonz wrote:
> I log into the box as myself and then run a bat file which includes:
> c:\nginx\Ru
Hello!
On Tue, Sep 09, 2014 at 02:25:15PM -0400, gthb wrote:
> Hello,
>
> Because uwsgi_cache_key has no default value (or rather, has the empty
> string as its default value), a configuration with uwsgi_cache set but
> uwsgi_cache_key not set behaves in a way that is very unlikely to be
> desir
Hello!
On Wed, Sep 10, 2014 at 10:30:55AM -0400, biazus wrote:
> Hey Guys,
>
> We have been using the latest stable Nginx version 1.6.1, and I've could
> notice that we might be facing a bug that was supposed to be fixed in
> version 1.5.11.
>
> Bugfix: the $upstream_status variable might conta
Hello!
On Wed, Sep 10, 2014 at 10:21:18AM -0400, nanochelandro wrote:
> Hello All,
>
> fastcgi_cache_use_stale is awesome, especially with "updating" parameter.
> But I have a feeling that it lacks a complementary parameter (or a separate
> setting to tune "updating" behaviour) that would instru
I log into the box as myself and then run a bat file which includes:
c:\nginx\RunHiddenConsole.exe C:\nginx\nginx.exe
ECHO Start php-cgi...
c:\nginx\RunHiddenConsole.exe C:\nginx\php-cgi-start.bat
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253161,253164#msg-253164
_
How are you staring nginx?
On September 10, 2014 3:22:24 PM GMT+01:00, ronlemonz
wrote:
>Nginx serves pages until I log off the web server. I need to log in
>again
>and start nginx (sometimes needing to kill IIS).
>Thanks for any thoughts,
>Ron
>
>Posted at Nginx Forum:
>http://forum.nginx.org/r
Hey Guys,
We have been using the latest stable Nginx version 1.6.1, and I've could
notice that we might be facing a bug that was supposed to be fixed in
version 1.5.11.
Bugfix: the $upstream_status variable might contain wrong data if the
"proxy_cache_use_stale" or "proxy_cache_revalidate" direct
Nginx serves pages until I log off the web server. I need to log in again
and start nginx (sometimes needing to kill IIS).
Thanks for any thoughts,
Ron
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,253161,253161#msg-253161
___
nginx mailing
Hello All,
fastcgi_cache_use_stale is awesome, especially with "updating" parameter.
But I have a feeling that it lacks a complementary parameter (or a separate
setting to tune "updating" behaviour) that would instruct nginx to quickly
return stale cached response also on first request (while fast
12 matches
Mail list logo
