Issue Bug Closed

#20780There's no feature to throw an HTTP 403 error when a page is not accessible by a user

JB 07/24/09, 15:33 updated 09/09/13, 11:13

Description

We’re having to show our users a 404 error because pageNotAccessible_handling only allows us to do so. We’d like to give our users an informative error along or a login form along with the correct HTTP response code rather than 404.

pageNotFoundAndExit() -> pageNotFoundHandler() -> pageErrorHandler()

t3lib_pageSelect::getPage() doesn’t distinguish between the different reasons for a page not being accessible
(issue imported from #M11579)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.