Ran across an installation we support where in production when someone tries to access a page after the stop publish date they are prompted to log in, but on test the same scenario shows the page to the user. I wasn't sure which was correct behavior since in both cases the page does have a published status so I created a demo site, set a page to expire, and on the demo site I was able to access the expired page without issue as well.
Is there a likely configuration issue?
Which behavior is correct?
Its an easy enough problem to solve by checking stop publish in the base page and redirecting if thats the case, but it seems like that should not be necessary.
The behavior is dependant on access rights. In order to see a page where the stop published date is passed, you need to be logged on as a user with at least edit access to that page. If you are not logged in and try to access such a page, the login screen is expected.
Per GunsarfsEPiServer Development Team
Same thing here.
Is there quick-fix configuration so hidden pages are redirected to "Page Not Found" error page instead of login page ?
Check out Mathias Kunto's blog post: http://blog.mathiaskunto.com/2012/04/03/think-things-through-or-simple-way-to-404-not-found-instead-of-episerver-login-screen-for-unpublished-pages/
Nice solution, thanks