Sitecore Stack Exchange is a question and answer site for developers and end users of the Sitecore CMS and multichannel marketing software. It only takes a minute to sign up.
Sign up to join this community
I know that there are solutions for this, and I have written some myself, but what I don't understand is why Sitecore doesn't redirect with 404 OOTB for page not found errors.
Does anyone know if there is a reason why Sitecore doesn't fix this chose to implement it this way and/or if there is any reason why they have patched it?
I'm not sure it's necessarily a case of that they won't fix it, it's just a case of priority. Like all development projects, they'll have a backlog of issues and features that they want to address, and how they go about prioritising them is up to them.
I'm not sure of the original decision behind the 302 redirect, and I can't think of a good reason why it should work like how it does. My honest guess would be that it was just built as a straight-forward redirect as a simple development approach, rather than a conscious decision to not account for correct status values. That is pure speculation on my part though. Though I'm supplying this as answer, someone maybe able to offer more insight here, if there is any to be had.
The best thing to do would be to make sure they're aware of it as something you'd like to see changed. Raise it on the UserVoice and also considering reaching out to support.
why Sitecore doesn't fix this- Only Sitecore knows. I can only assume that since this has been in Sitecore for a very long time, at the time it was not considered a SEO faux pas. – jammykam♦ Oct 18 '16 at 22:10