I'm guessing it would be tough for Heroku to implement custom error pages since when they're needed there's a problem with the stack that prevents routing to apps/accounts.
That said, I agree there's no reason for there to be Heroku branding in there. Just a simple, unbranded page for this status would be a great start. On Aug 5, 12:38 pm, Adrian Cuadros <adrian.cuad...@gmail.com> wrote: > I think we are all referring to the ouchie guy. > > Specifically when the heroku status is yellow and the apps just dont work. > > > > > > On Wed, Aug 4, 2010 at 3:31 AM, John Beynon <j...@beynon.org.uk> wrote: > > what errors are you referring too? You can change any Rails errors to > > custom errors - are you talking about the Back Log too deep messages > > and/or the 'Ouchie Guy'. You could argue that the BackLog too deep > > message isn't an error at all though. > > > John. > > > On Jul 27, 5:20 am, daniel hoey <danielho...@gmail.com> wrote: > > > Is there anyway to use our own error pages instead of the Heroku > > > ones? > > > -- > > You received this message because you are subscribed to the Google Groups > > "Heroku" group. > > To post to this group, send email to her...@googlegroups.com. > > To unsubscribe from this group, send email to > > heroku+unsubscr...@googlegroups.com<heroku%2bunsubscr...@googlegroups.com> > > . > > For more options, visit this group at > >http://groups.google.com/group/heroku?hl=en. > > -- > Adrian Cuadros > adr...@rutanet.com > (+521) 8116848310 -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to her...@googlegroups.com. To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
