Bug #20772
closed
pageNotFound_handling returns 301 instead of 404
0%
Description
Similar to bug described in http://bugs.typo3.org/view.php?id=3532
In a previous project within 4.2.6 the client gets redirected with an 404 error.
For a new project I used a fresh 4.2.8 installation and that's when the problem occurs:
if $TYPO3_CONF_VARS['FE']['pageNotFound_handling'] is set to a relative URL, than
$TYPO3_CONF_VARS['FE']['pageNotFound_handling_statheader'] is ignored and client is redirected to error page using code 302.
(issue imported from #M11561)
Updated by Chris topher about 14 years ago
Is that still an issue?
I just tested this with current trunk (4.5.0alpha3):
Currently you first get a redirect with statuscode 301 (not 302) and this leads you to the errorpage which I receive with statuscode 404. That is correct behaviour.
Updated by Tolleiv Nietsch over 13 years ago
- Category deleted (
Communication) - Status changed from Needs Feedback to Closed
- Target version deleted (
0)
Agree - should be fine after 4.4 - I close this issue for the sake of a clean bugtracker, feel free to open it again if this is still relevant in current TYPO3 versions.