Hi Charles,
IPv6 listeners can also accept IPv4 requests. This will result in IPs being
passed through to logs and such like :::192.168.123.101. If you do not
want this and do want both, add ipv6only=on to the IPv6 listen line.
Daniël
On Jul 26, 2016 02:25, "Charles Lawrence" wrote:
> I'm
If you're using a 1-config-per-site setup, then yes, you could. It
completely depends on your setup as to where you need to place it.
You can put it in any existing file that already has a server directive in
there. Just make sure none of the other server configs/files have the
default_server in t
Correct, you give the HSTS header on the SSL/TLS port. So if *any*
connection in the past has gone to the SSL/TLS port, the browser is forced
to use https:// for any future connection. You should set it to 1 for a
while and then disable it.
On Mar 20, 2015 9:48 AM, "jinwon42" wrote:
> Sorry.
>
>
I tried siege a lot, but could never get it to really use all cores on the
server, I found the tool wrk much more useful for load testing.
On Mar 18, 2015 2:31 AM, "halozen" wrote:
> 2 nginx 1.4.6 web servers - ocfs cluster, web root inside mounted LUN
> from SAN storage
> 2 MariaDB 5.5 servers -
