htaccess rewrite rules easy to generate, but nginx as new thing from ,2004, many people struggles at beginning.
Nginx 301 reduction rewrite rule
nginx old url to new url
generally we use wordpress plugins like redirect.
sub directory to parent directory redirection
nginx non www to www redirection
server { listen 80; server_name example.org; return 301 http://www.example.org$request_uri;}
server { listen 80; server_name www.example.org; # …}
One server block for redirection.
other sever block for application
rewrite vs return vs try_files
try files directive
directs the application server
nginx checks directories and file
and returns the $uri.(current uri request)(URI stands for Uniform Resource Identifier)
try files based on files index.php, index.html etc
try file $uri $uri/
if user requested web.com/text
then nginx looks text if not text/
Return
return just a simple form less programming scope less memory intensive
if pattern find just return this page.
useful to redirect old domain to new, old url to new.
server { listen 80;
server_name www.old-name.com;
return 301 $scheme://www.new-name.com$request_uri;
}
or
server{
root /var/www/html/oldsite
servername old.com
location\ {
return 301 http://google.com/$1
}
}
return 403 “service unavailable”
or
return 403;
return 3x, 1x,5x,4x codes
rewrite only 301, 302
return useful when it matches the server or location block.
for url forwardings
nginx rewrite module
when you use regex use this.
rewrite regex URL (flag);
regex (nginx has process before it’s going for server block)
nginx rewrite module,
1st process regex, and look for directives like break,last, permanent,if,return,set
flags, rewrite etc
permanent =301
last; tells nginx to stop current block and search new block(server, location)
break=
Wildcard redirection in nginx
converting htaccess rules to nginx rewrite rules
nginx variables
$scheme protocol http or https
$request_uri full uri including arguments
The $1 and $2 variables capture the path elements that aren’t changing.
$request_uri vs $1 variables
set $someword $1 ;
custom variable ($1) that in fact is equivalent to the built‑in $request_uri variable
Nginx regex modifiers
location =/test
not applies to site.com/test/tdd/
no modifier
location /test
applies to site.com/test/,
~ operator
case-sensitive match
location ~ ^/test$
^ starts with ,
$ ends with
not applies to /TEST
~* operator (case insensitive)
location ~* ^/abcd$
applies to /TEST
^~ modifier
string should be match at beginning if the requested uri
starts with specific & case sensitive
~ or ~* requested uri & location block should be match
location ~* ^/document$ {
[…] # requests exactly matching “/document”
location ~* /myapp/.+\.php$ { #… }
asterisk after the tilde (~*) makes the match case insensitive.
URI ending with myapp/file.php, such as /test/myapp/hello.php and /myapp/hello.php.
case‑insensitive test of the regex (.*myapp)/(.+\.php)$ against the URI /myapp/hello.php:
location ~* (.*/myapp)/(.+\.php)$ { #…}
understanding nginx regex operators
^ matches starts with
$ matches empty string at the end
~
(.*)regex group
.* matches all
\* matches everything after \
?
rewrite ^/(.*)\.(png|jpg|gif)$
startswith/anystringgouped&endswith.(png|jpg|gif.
~^(www)\.example\.com$; # $1 = www
amp to non amp conversion
location