January 10, 2020 03:03PM
Hi Team,

I have a funny situation that I can't seem to get around. Here are the details.

We had this naming convention to indicate a specific location: https://myurl/location/index.php?id=235
This naming convention is still out in the internet ether
We changed to go to a slug based operation: https://myurl/location/newyorkcity
We do the work to determine that id=235 is really the newyorkcity location in the code
We return back to the client, the correct url (https://myurl/location/newyorkcity)

When we review the SEO around this old url, we are getting back a 302, that it's temporary.

how can I tweak the nginx engine to force a 301.

thanks
Subject Author Posted

Force 302 to 301 redirect

tconlon January 10, 2020 03:03PM

Re: Force 302 to 301 redirect

cooley.josh@gmail.com January 10, 2020 03:11PM

Re: Force 302 to 301 redirect

tconlon January 10, 2020 03:17PM

Re: Force 302 to 301 redirect

Francis Daly January 10, 2020 06:04PM

Re: Force 302 to 301 redirect

tconlon January 11, 2020 08:29AM

Re: Force 302 to 301 redirect

tconlon January 11, 2020 08:35AM

Re: Force 302 to 301 redirect

Francis Daly January 11, 2020 09:20AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 56
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready