-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 8/17/16 4:12 PM, Dr James Smith wrote:
> It may be possible to write your own auto-renewal script
> relatively easily for LetsEncrypt. I have done for Apache as (a) I
> don't use the standard paths and setup, (b) I wish to use HPKP on
> my
It may be possible to write your own auto-renewal script relatively
easily for LetsEncrypt. I have done for Apache as (a) I don't use the
standard paths and setup, (b) I wish to use HPKP on my servers for
additional security and "Lets Encrypt" auto scripts generate a new key
each time which
It seemed like the auto-renewal process for ssl from LetsEncrypt is not
supported yet for nginx, at least according to this article on its
publication date:
https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-16-04
My needs are really simple and I
Folks;
we use an apache2.4 and mod_proxy_balancer in front of various backend
systems that aren't per se able to deal with load balancers in front of
them so we use the approach outlined in [1] and mod_headers to set a
ROUTEID cookie.
What so far I was unable to figure out: How does this setup
Depends on your backends - nginx is good if it is serving primarily
static files and or proxying back to quick responding backends. It seems
to be less well suited to slower/heavier backends. Apache always seems
to work - slower mind you - but always seems to work... So if
reliability is your
why did not you use nginx anyway? should be faster and modern. did not
have the chance to try that yet myself. still using apache everywhere.
On 17 August 2016 at 03:18, R wrote:
> Ugh sorry, I had a test installation of nginx on the machine, which was not
> fully