Hello!
On Thu, Nov 27, 2014 at 12:07 AM, VladimirSmirnov wrote:
> P.S. As pointed by resty.session author, I've disabled ssl_session_ticket
> and now I'm receiving ssl_session_id even with TLS enabled. But I'm not sure
> that it's best way to deal with this problem.
>
No, you don't really want th
Hi,
Thank you for responding, Styopa.
At the time my server was setup, Ubuntu 12.04's repositories were outdated,
so I added a repository with the latest development version of nginx, which
was as stable and supported as a final release, and by default the web files
were located in /usr/share/ng
On Fri, Nov 28, 2014 at 02:00:32PM +, Ian Winter wrote:
Hi there,
> I understand that part, what I mean is separating the entries like you’d have
> with flat files, so if you had;
>
> domaina => log/domaina_access
> domainb => log/domainb_access
>
> That kind of setup, but, with syslog so
maybe switch to using Wordpress Super Cache ? handled blitz.io 8000 user
stress test fine with Nginx 1.7.7, PHP-FPM 7.0.0-dev, MariaDB 10.0.x and
CentOS 7.0 = 237 million hits/day on 2GB DigitalOcean KVM VPS server
http://wordpress7.centminmod.com/74/wordpress-super-cache-benchmarks-blitz-io-load-t
I understand that part, what I mean is separating the entries like you’d have
with flat files, so if you had;
domaina => log/domaina_access
domainb => log/domainb_access
That kind of setup, but, with syslog so it’s easier to identify where they’ve
come from.
Right now we have one nginx.access.
Hi Francis,
Thank you for the suggestions. I will try them and revert.
Regards,
Joyce Babu
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
