London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
This is the default behavior of this Epi module. You can implement the customizations mentioned on the git hub page to add controller and use the attribute (on your action that will return your custome view)
[NotFoundPage]
This will set status code for you to 404.
Hello. My new site has the issue discussed here:
https://world.episerver.com/forum/developer-forum/-Episerver-75-CMS/Thread-Container/2018/11/404-behaviour-inconsistent/
That thread doesn't seem to contain the info I need.
Specifically, a request for a missing page results in the user seeing a nice message, but no 404 status code is sent. Instead, it's sending 200. I need to fix this, per Google's guidelines seen here.
https://developers.google.com/search/docs/advanced/crawling/custom-404-pages
How do I set up the handler to emit the correct status code of 404?
Thanks.