On 11/29/2016 09:55 AM, Lukas Tribus wrote:
It seems that search engines are probing https: even for sites that
don't offer it
Which is fine.
just because it's available for others, with the end
result that pages are being attributed to the wrong site.
Sounds like an assumption. Any rea
Francis Daly Wrote:
---
> On Wed, Nov 23, 2016 at 01:22:42PM -0500, Sushma wrote:
>
> Hi there,
>
> > I understand that proxy_set_header sets headers before proxying the
> > request to the upstream server.
>
> proxy_set_header adds extra http h
Just a personal preference, but i put an https version in front of all
sites(and redirect 80 to 443) and keep the certs up to date for free with
lets-encrypt/certbot (i have nothing to do with the company), with SNI,
one IP. This is simple as I keep the nginx configurations up to date with
a confi
> It seems that search engines are probing https: even for sites that
> don't offer it
Which is fine.
> just because it's available for others, with the end
> result that pages are being attributed to the wrong site.
Sounds like an assumption. Any real life experience and
evidence backing t
This is more a philosophical than technical question I suppose.
Is it necessary to purchase a SSL cert for all domains sharing an IP
address if one of them uses https?
It seems that search engines are probing https: even for sites that
don't offer it, just because it's available for others, w
