Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When building web applications should error pages (400, 500 status codes) be static .html files or is it fine to serve up dynamic pages and why?
I would think that if your server goes down, your dynamic pages would go down with it. At least with static pages, your load balancer could serve up static files.
As far as the HTTP protocol is concerned, there is no difference between a static and a dynamic page, so standards wise, there is no problem in serving up a dynamic page for a 400 and 500.
However, as you say, if there is an error in your application, then trying to serve up a dynamic page is probably not the best idea as it will possibly fail due to the same error, or even exacerbate the problem if the error is due to database congestion etc.