Download
1 / 4
40 likes | 143 Views
In Magnolia CMS, users face an issue where redirects always return a 302 status code, regardless of the selected 301 option. This behavior can lead to incorrect server responses, causing problems with SEO and user experience. Although the redirects appear to work initially, a deeper inspection reveals the mismatch in expected response codes. This article will explore potential causes, troubleshooting steps, and solutions to ensure that your redirects work as intended and return the correct HTTP status codes.
E N D
Magnolia Redirects not working as intended When creating a redirect the server will always respond with a 302, even when selecting 301 in the select box.
... The server response is wrong • At a glance, the redirect is working but if you look at the response code it returns a 302, which is NOT what we selected in the properties.
