Nginx – forcing nginx to redirect to server root

nginxredirectrewrite

I have the following line in nginx:

try_files $uri $uri/ /index.html;

As far as I understand, it rewrites all queries to files that are not found to index.html.
Meaning, that index.html?foo=bar and idontexist.html?foo=bar leave the same result which screws up Google crawling.

How can I not rewrite but redirect to the default url?

The perfect solution would be even without the index.html.
So http://domain.com/idontexist.html?foo=bar would redirect using 301 to http://domain.com/?foo=bar

Best Answer

location / {
    try_files $uri $uri/ @to_home;
    ...
}

location @to_home {
    return 301 /$is_args$args;
}

Related Solutions

Nginx rewrite rule for using domain host to redirect to specific internal directory

This is best accomplished using three servers:

# www.domain.com, actually serves content
server {
  server_name www.domain.com;
  root /doc/root;

  # locations, etc
}

# redirect domain.com -> www.domain.com
server {
  server_name domain.com;
  rewrite ^ http://www.domain.com$request_uri? permanent;
}

# handle anything.domain.com that wasn't handled by the above servers
server {
  # ~ means regex server name
  # 0.8.25+
  #server_name ~(?<city>.*)\.domain\.com$;

  # < 0.8.25
  server_name ~(.*)\.domain\.com$;
  set $city $1;

  location = / { rewrite ^ http://www.domain.com/$city/prelaunch; }
  location = /landing { rewrite ^ http://www.domain.com/$city/prelaunch; }
  # should there be a /$city before $request_uri?
  location / { rewrite ^ http://www.domain.com$request_uri?; }
}

nginx try_files – How Does try_files Work in nginx?

try_files tries the literal path you specify in relation to the defined root directive and sets the internal file pointer. If you use for instance try_files /app/cache/ $uri @fallback; with index index.php index.html; then it will test the paths in this order:

$document_root/app/cache/index.php
$document_root/app/cache/index.html
$document_root$uri

before finally internally redirecting to the @fallback named location. You can also use a file or a status code (=404) as your last parameter but if using a file it must exist.

You should note that try_files itself will not issue an internal redirect for anything but the last parameter. Meaning you cannot do the following: try_files $uri /cache.php @fallback; as that will cause nginx to set the internal file pointer to $document_root/cache.php and serve it, but since no internal redirect takes place the locations aren't re-evaluated and as such it will be served as plain text. (The reason it works with PHP files as the index is that the index directive will issue an internal redirect)

Best Answer

Related Solutions

Nginx rewrite rule for using domain host to redirect to specific internal directory

nginx try_files – How Does try_files Work in nginx?

Related Topic