Related

NGINX Config Generator Tool

Easily configure a performant, secure, and stable NGINX server.

 Learn More
What is the virtual host configuration for a ZF3 application with nginx? Question Question
It has been 3 days and my domain is still not active Question Question

Question

Correct way to write 301 redirect?

Posted February 22, 2019 932 views
NginxUbuntu 18.04

My question is in regards to the correct way to write a 301 redirect from requests to our old site URLs. When we go live, we need the following redirect:

(.*)mydomain.com/index.php(.*)  —>  https://mydomain.com/home

In other words, any request that starts with: 

should be redirected to https://mydomain.com/home.

My idea for how to do this would be to put the following line in our server block: 

server {
    . . .
    server_name mydomain.com;
    rewrite ^/index.php/(.*)$ https://mydomain.com/home permanent;
    . . .
}

Is this correct? Thanks!

Add a comment
avebury
By:
avebury

Related

NGINX Config Generator Tool

Easily configure a performant, secure, and stable NGINX server.

 Learn More
What is the virtual host configuration for a ZF3 application with nginx? Question Question
It has been 3 days and my domain is still not active Question Question

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer
AHA February 22, 2019

Two or three potential issues I see:

Trailing slash: When you have…

rewrite ^/index.php/(.*)$ https://mydomain.com/home permanent;

nginx is only going to match on URLs like:

Remove the trailing slash to match standard URLs like the ones you listed

rewrite ^/index.php(.*)$ https://mydomain.com/home permanent;

WWW/Non-WWW: if you want one server block to catch WWW/Non-WWW, you have to make sure your server_name block is catching both:

server_name www.mydomain.com mydomain.com;

or to catch all host variants:

server_name _;

HTTP/HTTPS: You may also need to ensure your server block is catching requests on HTTP port (80) and HTTPS (443). You should have listen lines that include ports 80 and 443

listen 80 default_server;
listen [::]:80 default_server ipv6only=on;
listen 443 ssl;
listen [::]:443 ssl;

(they don’t always look exactly like this, for example ipv6only=on; isn’t always there.) The reason there are two lines for each is [::]:80 is matching port 80 in an IPV6 request.

Reply Report

Related

Looking for something else?

Ask a new question Search for more help