This project is archived and is in readonly mode.
Failsafe middleware doesn't render 500.html as ERB
-
Hongli Lai
- Tag set to 2-3-stable
-
Hongli Lai
Issue #2716 Default ShowExceptions error message is not friendly enough has a similar patch, but for Rails 3.0.
-
CancelProfileIsBroken
ERB was removed from 500.html in 81c7a5d48d972c9e3973b4c018fafae1dfd9c0de and the code to render it was removed in 10b6073968eb43a3e20efd352d97d08720beeb12
-
josh
- Assigned user set to josh
- State changed from new to open
- Milestone cleared.
-
Hongli Lai
Hm, I see. But it's still a huge usability issue. "Help my app says that something went wrong but I don't know what to do!" is one of the most often asked questions, and especially people who have little prior experience with administering Unix systems do not know that they're supposed to look in log files.
Here's a new patch. It removes the ERB rendering but it retains the improved error messages.
-
Pratik
We shouldn't put "(If you're the administrator of this website, then please read this application's log file and/or the web server's log file to find out what went wrong.)" message. Especially after "we've been notified".
-
Hongli Lai
What do you think would be the best message?
-
Jeremy Kemper
I think it's a good change that gently pushes new Rails devs the right direction. Most production apps have replaced their 500.html with something better anyway.
-
Repository
- State changed from open to resolved
(from [34a1ed0df8311aba350043ec7ef373da3058855f]) Make the Failsafe middleware attempt to render 500.html during failsafe response rendering. Also make the default static failsafe response more friendly, in case 500.html rendering fails. [#2715 Failsafe middleware doesn't render 500.html as ERB state:resolved]
Signed-off-by: Joshua Peek josh@joshpeek.com
http://github.com/rails/rails/commit/34a1ed0df8311aba350043ec7ef373...
