Symphony.

At the moment Symphony sends the following HTTP header status lines when in maintenance mode:

• using the generic maintenance page: HTTP 1.0 500 Server Error
• using a page of type “maintenance”: HTTP 1.1 200 OK

Shouldn’t it be something like HTTP/1.1 503 Service Unavailable in both cases?

This is tricky, it depends on how the maintenance mode is used. We’ve had instances where a website is using maintenance mode to throw up a “pre-air” TV program landing page. In this case, perhaps 503 isn’t ideal.

I think the maintenance extension should allow for configurable header status. For a long term solution, we need to look at extending the page type system in the core to allow for arbitrary header returns for pages and have them decoupled from page “labels”.

Well, I see. But people should be aware of Search engine spiders. If you send a “200 OK” header, the crawler will think that this is it…

Shouldn’t the generic maintenance page send a 503 header anyway?

Allen, for the Moment I solved my issue with a short extension called HTTP Status Line Mappings.

But, yes, we should have more flexibility here. Maybe most of those special headers (like 404, XML etc.) should be removed from the core?

[EDIT]: Sorry for the double post.