Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

No 500 status code on errors

Go to End

2 Posts   761 Views


Community Member, 176 Posts

20 December 2011 at 9:44pm

I received an error report from one of my users, but they forgot to note on which page. I tried doing a link check with Xenu to identify it, only to discover that if an error occurs on a page no 500 (or other) http status code is returned. It still returns a 200 page status code.

Is this intentionally? I would think the appropriate error code should be returned instead?


Community Member, 473 Posts

20 December 2011 at 10:26pm

SilverStripe is only able to return the error if it's something that it can catch. Things like parse errors and timeouts can't be caught by SilverStripe, so the server responses with any output and the default status code of 200.