On Sun, Jul 30, 2017 at 12:56:55PM +0300, ST wrote:
Hi there,
> Is it a good idea to use DNS forwarding in order not to obtain/install
> ssl keys for example.com as we don't plan to use it? This should make
> redirection faster and requires no setup on nginx... Are there any down
> sides of such
PPS:
my fault: there is no ssl key info so obviously it should not work. At
least for those server name listed inside first server{} (strange is
that https://example.org - server{} three also stops working...)
Is it a good idea to use DNS forwarding in order not to obtain/install
ssl keys for exa
PS:
actually merely adding "listen 443 ssl;" to the first server causes the
same error (curl: (35) Unknown SSL protocol error in connection to
www.example.org:443)
server {
listen 443 ssl;
server_name www.example.org example.com; # and some more domains
return 301 https://example.org$request_u
Hi Francis,
thank you for the detailed answer...
I tried to take care of the first problem by doing this:
server {
listen 80;
listen 443 ssl;
server_name www.example.org example.com; # and some more domains
return 301 https://example.org$request_uri;
}
But the site stopped working all toget
On Fri, Jul 28, 2017 at 02:13:23PM +0300, ST wrote:
Hi there,
> server {
> server_name www.example.org example.com; # and some more domains
> return 301 $scheme://example.org$request_uri;
> }
>
> server {
> listen 80;
> server_name example.org;
> ...
> if ($http_user_agent !~ facebookexter
Hello,
I have several questions related to redirects:
Here is my setup:
server {
server_name www.example.org example.com; # and some more domains
return 301 $scheme://example.org$request_uri;
}
server {
listen 80;
server_name example.org;
...
if ($http_user_agent !~ facebookexternalhit/1.
