I did a replace on OpenSSL using YUM which should have removed all of the
existing 0.98 version I presume. Nginx was a clean install (from source) so
shouldnt have clashed with anything?
I'm not sure where to go from here, nothing in the error logs. Previously
when I tried to run spdy/nginx and th
On Friday 05 July 2013 19:05:58 benseb wrote:
> The compile command I used was:
>
> --user=nginx --group=nginx --prefix=/usr/share/nginx
> --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf
> --error-log-path=/var/log/nginx/error.log
> --http-log-path=/var/log/nginx/access.log
> --http-
[ben@lb-3 ~]$ ldd /usr/sbin/nginx
linux-vdso.so.1 => (0x7fffbe7ff000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x7fe08af81000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x7fe08ad49000)
libpcre.so.0 => /lib64/libpcre.so.0 (0x7fe08ab1d000)
libss
Yes - if you tell me how?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240545,240610#msg-240610
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Can you run ldd against the nginx executable?
Lukas
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
The compile command I used was:
--user=nginx --group=nginx --prefix=/usr/share/nginx
--sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf
--error-log-path=/var/log/nginx/error.log
--http-log-path=/var/log/nginx/access.log
--http-client-body-temp-path=/var/lib/nginx/tmp/client_body
--http-
On Friday 05 July 2013 18:35:04 benseb wrote:
> It was installed via yum -(IUS)
>
> I installed both OpenSSL10 and openssl10-libs.x86_64 : A general purpose
> cryptography library with TLS implementation
>
>
> [root@lb-3 ~]# openssl version -a
> OpenSSL 1.0.1e 11 Feb 2013
> built on: Wed Feb 13
Also, does this help?
[root@lb-3 ~]# nginx -V
nginx version: nginx/1.4.1
built by gcc 4.4.7 20120313 (Red Hat 4.4.7-3) (GCC)
TLS SNI support enabled
See 'TLS NSI support enabled'?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240545,240605#msg-240605
___
It was installed via yum -(IUS)
I installed both OpenSSL10 and openssl10-libs.x86_64 : A general purpose
cryptography library with TLS implementation
[root@lb-3 ~]# openssl version -a
OpenSSL 1.0.1e 11 Feb 2013
built on: Wed Feb 13 11:31:32 EST 2013
platform: linux-x86_64
options: bn(64,64) md2
On Sunday 30 June 2013 04:03:08 ctrlbrk wrote:
> ctrlbrk Wrote:
> ---
>
> > BTW, I use
> >
> > fastcgi_buffers 16 2048k;
> > fastcgi_buffer_size 2048k;
> > fastcgi_busy_buffers_size 2048k;
> >
> > So I am under the 16MB, unless you are applying
Congrats Igor and Nginx team. :-)
It just matter of time before Nginx becomes #1 in Top 10,000 and eventually
#1 overall.
Most cheap hosting companies are run by non-techie people (using resellers
tool) who don't understand benefit of Nginx and/or do not have control on
server softwares!
Posted
No it doesn't look like limit_except will allow me to change behaviour of
proxy timeouts or next_upstream based on the HTTP method. Are there any
recommendations on how this could be done aside from my workaround?
On Fri, Jul 5, 2013 at 9:27 AM, Branden Visser wrote:
> Thanks for the quick repl
Thanks for the quick reply Maxim. That looks interesting, though in
particular proxy_next_upstream and proxy_read_timeout don't report to be
valid in that context. I'll give it a try, perhaps it's just an error in
the docs.
On Fri, Jul 5, 2013 at 9:02 AM, Maxim Dounin wrote:
> Hello!
>
> On Fri
Dear list,
This is going to be a long post, but I hope you will bear with me. I
am trying to find a way to run Topincs, an agile web application
framework based on Topic Maps paradigm, on nginx. Topincs is a
typical LAMP app, so I hoped I would be able to figure it out on my
own, but unfortunatel
Hello!
On Fri, Jul 05, 2013 at 08:32:38AM -0400, Branden Visser wrote:
> Hi all,
>
> I was wondering if there is a way to have different proxy_* rules depending
> on the HTTP method? My use case is that I want to be a little more
> conservative about what requests I retry for POST requests, as t
Hi all,
I was wondering if there is a way to have different proxy_* rules depending
on the HTTP method? My use case is that I want to be a little more
conservative about what requests I retry for POST requests, as they have an
undesired impact if tried twice after a "false" timeout.
e.g., for GET
The problem still exists. You can only see the album thumbnails but it
should be possible to click on them to see all pictures from an album and
then see them in full screen.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240504,240594#msg-240594
___
No, the problem is not solved: You can see the album thumbnails but when you
click on them there should be a page with the different pictures from that
album which you can view in full screen mode.
You can see how it should work on http://wp.oopstouch.com/?page_id=22 and I
think the problem is rel
18 matches
Mail list logo
