Force 302 to 301 redirect

tconlon nginx-forum at forum.nginx.org
Fri Jan 10 20:03:18 UTC 2020


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

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,286700,286700#msg-286700



More information about the nginx mailing list