AW: AW: AW: AW: SNI and certs.

> Why should I? I clearly defined the problem/misconfiguration. I don't > really see the need to justify why I want to fix it. To help others, myself included to comprehend a possible problem in similar configurations and learn more about it. After all, this is a community. > Well, you told me

Rewrite rules

Hi there, i try to setup some rules. I have to rules which conflicts. rewrite ^/(.*?)/(.*?)/(.*)$ /$3; #rewrite ^/$ /a/b permanent; the first Rules is needed from our developer the second rules os for a request. The Goal is to redirect all request on any domain.com to any

Re: AW: AW: AW: SNI and certs.

On 11/30/2016 09:17 AM, Lukas Tribus wrote: Does it cause warnings in the webmaster tools? Who cares? Does it affect your ranking? I doubt it. Does it index pages or error pages from the default website and assign to your website? I doubt that even more. Does it upset my customer? YES. That's

AW: AW: AW: SNI and certs.

> > Does it cause warnings in the webmaster tools? Who cares? > > Does it affect your ranking? I doubt it. > > Does it index pages or error pages from the default website and assign to > > your website? I doubt that even more. > > Does it upset my customer? YES. > > That's all the justification I

Re: AW: AW: SNI and certs.

On 11/29/2016 09:28 PM, Lukas Tribus wrote: What I don't see is why and how that would be a problem, even when HTTPS is not properly setup for that particular domain. Does it cause warnings in the webmaster tools? Who cares? Does it affect your ranking? I doubt it. Does it index pages or error

Re: AW: SNI and certs.

There's no "nice" way to handle this in nginx as far as I'm aware. I think the best setup is a default vhost with a generic (server hostname?) certificate, and for any bots or clients that ignore the common name mismatch you can return the 421 Misdirected Request code. https://httpstatuses.com/421

Re: Nginx headers to be set at the time of request processing

On Mon, Nov 28, 2016 at 06:56:29PM -0500, CeeGeeDev wrote: Hi there, Thanks for expanding on what you are doing. I confess that I am still not sure what it is; but that's ok -- I don't need to understand. > So for the benefit of the community: our plan is to implement a custom > configuration d

AW: AW: SNI and certs.

> > Any real life experience and evidence backing this? > yes Care to elaborate? > Not sure why you're doubting me here Lukas. Yes, this is a problem. No > I'm not making it up. We know that crawlers like Googlebot try HTTPS as well, even if there is no https link towards the website. That is

Drupal 7, nginx with ModSecurity - How to resolve that 404 error page please?

Hello all, I have installed Drupal 7 on latest version of Nginx web server which was compiled with support of ModSecurity module. I have activated core OWASP rule set. But when I active ModSecurity in my virtual host config file for my Drupal 7 web I do not login, register or reset password with t