Possible to turn custom error pages *off*?
Hi guys, I'm new to Heroku, so apologies if this has been covered before (searched the group and didn't find anything). The subject says it all, but I also posted this question on Stack Overflow with more detail: http://stackoverflow.com/questions/10551393/heroku-possible-to-turn-custom-error-pages-off Thanks in advance for any help! =) Aseem -- You received this message because you are subscribed to the Google Groups "Heroku" group. 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_US?hl=en
Re: Custom Error Pages problem
Thanks for the report Joseph, we'll look into it. Adam -- 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.
Custom Error Pages problem
The custom error pages solution puts our content in an iframe, and that iframe has a height=100% This does not work in all browsers. In Firefox the iframe is only ~100px tall no matter the size of my window. To size an iframe to its content (or to the browser window more likely), you'll have to use javascript in the custom error pages solution. -- 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.
Re: Custom error pages, we *really* need them
+1 for iframe/javascript solution I feel like the same system could be used to improve the custom maintenance mode page as well. I tested it out on my staging app the other day, and it took 15 minutes before the ugly default page was replaced by my custom page. Thats just too long! My biggest downtime for a production migration so far downtime is less than 5 minutes, which means nobody will ever see my custom page. -- 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.
Re: Custom error pages, we *really* need them
+1 -- I've been waiting for this one for a loong time. On Sep 16, 2:06 am, Daniele wrote: > A separate branch or a dedicated folder are not a solutions. > When a system wide problem occurs (as 2 days ago) the dyno grid and > probably the routing mesh too are broken, so all the "logic" part of > the system is unavailable. Heroku can only serve a generic page. > Perhaps it can personalize it with the request headers (es. domain > name) but no more. > So an iframe or an ajax setup is the only way. > > Different address for the message 'backlogged to deep" that could be > personalized using a specific folder/file. But we have to point out > when it pop up: during the system's problem phase I get a lot of these > messages while the git repo was not probably accessible. So I will > prefer an iframe/ajax solution in this case too. > > Daniele > > On Sep 15, 7:19 pm, Mike Abner wrote: > > > > > Why have a separate branch? Heroku can just tell us where to put them > > in the folder hierarchy and they'll grab them from there. -- 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.
Re: Custom error pages, we *really* need them
A separate branch or a dedicated folder are not a solutions. When a system wide problem occurs (as 2 days ago) the dyno grid and probably the routing mesh too are broken, so all the "logic" part of the system is unavailable. Heroku can only serve a generic page. Perhaps it can personalize it with the request headers (es. domain name) but no more. So an iframe or an ajax setup is the only way. Different address for the message 'backlogged to deep" that could be personalized using a specific folder/file. But we have to point out when it pop up: during the system's problem phase I get a lot of these messages while the git repo was not probably accessible. So I will prefer an iframe/ajax solution in this case too. Daniele On Sep 15, 7:19 pm, Mike Abner wrote: > Why have a separate branch? Heroku can just tell us where to put them > in the folder hierarchy and they'll grab them from there. -- 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.
Re: Custom error pages, we *really* need them
Why have a separate branch? Heroku can just tell us where to put them in the folder hierarchy and they'll grab them from there. If I were designing this I'd say to create a top level directory in your project called "errors" or "heroku_error_pages" or something like that. Then name you're files like you do for rails error pages...500.html, etc. When you deploy I'd take those pages and copy them to a static html host server while renaming them to _error_xxx.html. Then the heroku infrastructure could simply redirect to that location instead of returning the generic error pages. Heroku knows which error it is and it knows what application was being accessed, so this should be relatively simple. I live across the street. Want me to come in and implement it real quick? ;o) Mike On Wed, Sep 15, 2010 at 10:00 AM, David Balatero wrote: > I've suggested in the past having a separate branch in your repo called > "errorpages" or something, which has a few static HTML pages. Push that > branch to Heroku, and it can use those files to serve errors. > On Wed, Sep 15, 2010 at 7:58 AM, Daniel Spangenberg > wrote: >> >> I like the idea too, >> but maybe I don't wan't to set up an extra heroku app or shared host for >> an static html page only, >> maybe it would be nice if you can choose to take the iframe and a >> textinput, where you can insert plain html. >> Daniel >> Am 15.09.2010 um 16:55 schrieb Adrian Cuadros: >> >> + 1 on this also. like the idea about the iframe >> >> On Wed, Sep 15, 2010 at 9:02 AM, Jeff Schmitz >> wrote: >>> >>> +1 Maybe the generic page could be a fail Koi >>> >>> On Wed, Sep 15, 2010 at 7:31 AM, Daniele wrote: Hi, as you can see from the status page in the past 2 days Heroku had a lot of problems that resulted in "Timeout connection" and "Backlog Too Deep" error pages. This two pages have a message specifically addressed to the administrator that is not acceptable in a production site. We need to have personalized pages. Same logic about the Heroku Ouchie Page of course! If this is not possible immediately a quick hack could be to have a really generic "white-label" page (multilingual would be appreciated) and put all the system message in an html comment. We are tech guys, right? Is not a problem to look at the source to find out what is happening. This seems clever that show a ugly error message to everyone. Finally as I already suggested in another discussion: A simple solution for more personalization without the need to access any preferences could be to have a full page iframe inside the heroku's error page pointing to http://error./.html The admin has to create a third/fourth level domain, point it to a different server and create the personalized pages. So every application can have an error page/backup application to handle the down. A js can check for the domain existence and switch to a plain txt message if it is not set. I'd love to get feedback on these ideas by Heroku guys. Thank you. Daniele -- 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. >>> >>> >>> -- >>> 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. >> >> >> >> -- >> 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. >> >> -- >> 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. > > -- > 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. > -- You receiv
Re: Custom error pages, we *really* need them
I've suggested in the past having a separate branch in your repo called "errorpages" or something, which has a few static HTML pages. Push that branch to Heroku, and it can use those files to serve errors. On Wed, Sep 15, 2010 at 7:58 AM, Daniel Spangenberg < daniel.spangenb...@googlemail.com> wrote: > I like the idea too, > but maybe I don't wan't to set up an extra heroku app or shared host for an > static html page only, > maybe it would be nice if you can choose to take the iframe and a > textinput, where you can insert plain html. > > Daniel > > Am 15.09.2010 um 16:55 schrieb Adrian Cuadros: > > + 1 on this also. like the idea about the iframe > > On Wed, Sep 15, 2010 at 9:02 AM, Jeff Schmitz > wrote: > >> +1 Maybe the generic page could be a fail Koi >> >> >> On Wed, Sep 15, 2010 at 7:31 AM, Daniele wrote: >> >>> Hi, >>> as you can see from the status page in the past 2 days Heroku had a >>> lot of problems that resulted in "Timeout connection" and "Backlog Too >>> Deep" error pages. This two pages have a message specifically >>> addressed to the administrator that is not acceptable in a production >>> site. We need to have personalized pages. Same logic about the Heroku >>> Ouchie Page of course! >>> >>> If this is not possible immediately a quick hack could be to have a >>> really generic "white-label" page (multilingual would be appreciated) >>> and put all the system message in an html comment. We are tech guys, >>> right? Is not a problem to look at the source to find out what is >>> happening. This seems clever that show a ugly error message to >>> everyone. >>> >>> Finally as I already suggested in another discussion: >>> A simple solution for more personalization without the need to access >>> any preferences could be to have a full page iframe inside the >>> heroku's error page pointing to http://error >>> ./.html >>> The admin has to create a third/fourth level domain, point it to a >>> different server and create the personalized pages. >>> So every application can have an error page/backup application to >>> handle the down. A js can check for the domain existence and switch to >>> a plain txt message if it is not set. >>> >>> I'd love to get feedback on these ideas by Heroku guys. Thank you. >>> >>> Daniele >>> >>> -- >>> 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. >>> >>> >> >> -- >> 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. >> > > > > -- > 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. > > > -- > 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. > -- 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.
Re: Custom error pages, we *really* need them
I like the idea too, but maybe I don't wan't to set up an extra heroku app or shared host for an static html page only, maybe it would be nice if you can choose to take the iframe and a textinput, where you can insert plain html. Daniel Am 15.09.2010 um 16:55 schrieb Adrian Cuadros: > + 1 on this also. like the idea about the iframe > > On Wed, Sep 15, 2010 at 9:02 AM, Jeff Schmitz > wrote: > +1 Maybe the generic page could be a fail Koi > > > On Wed, Sep 15, 2010 at 7:31 AM, Daniele wrote: > Hi, > as you can see from the status page in the past 2 days Heroku had a > lot of problems that resulted in "Timeout connection" and "Backlog Too > Deep" error pages. This two pages have a message specifically > addressed to the administrator that is not acceptable in a production > site. We need to have personalized pages. Same logic about the Heroku > Ouchie Page of course! > > If this is not possible immediately a quick hack could be to have a > really generic "white-label" page (multilingual would be appreciated) > and put all the system message in an html comment. We are tech guys, > right? Is not a problem to look at the source to find out what is > happening. This seems clever that show a ugly error message to > everyone. > > Finally as I already suggested in another discussion: > A simple solution for more personalization without the need to access > any preferences could be to have a full page iframe inside the > heroku's error page pointing to > http://error./.html > The admin has to create a third/fourth level domain, point it to a > different server and create the personalized pages. > So every application can have an error page/backup application to > handle the down. A js can check for the domain existence and switch to > a plain txt message if it is not set. > > I'd love to get feedback on these ideas by Heroku guys. Thank you. > > Daniele > > -- > 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. > > > > -- > 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. > > > > -- > 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. -- 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.
Re: Custom error pages, we *really* need them
+ 1 on this also. like the idea about the iframe On Wed, Sep 15, 2010 at 9:02 AM, Jeff Schmitz wrote: > +1 Maybe the generic page could be a fail Koi > > > On Wed, Sep 15, 2010 at 7:31 AM, Daniele wrote: > >> Hi, >> as you can see from the status page in the past 2 days Heroku had a >> lot of problems that resulted in "Timeout connection" and "Backlog Too >> Deep" error pages. This two pages have a message specifically >> addressed to the administrator that is not acceptable in a production >> site. We need to have personalized pages. Same logic about the Heroku >> Ouchie Page of course! >> >> If this is not possible immediately a quick hack could be to have a >> really generic "white-label" page (multilingual would be appreciated) >> and put all the system message in an html comment. We are tech guys, >> right? Is not a problem to look at the source to find out what is >> happening. This seems clever that show a ugly error message to >> everyone. >> >> Finally as I already suggested in another discussion: >> A simple solution for more personalization without the need to access >> any preferences could be to have a full page iframe inside the >> heroku's error page pointing to http://error >> ./.html >> The admin has to create a third/fourth level domain, point it to a >> different server and create the personalized pages. >> So every application can have an error page/backup application to >> handle the down. A js can check for the domain existence and switch to >> a plain txt message if it is not set. >> >> I'd love to get feedback on these ideas by Heroku guys. Thank you. >> >> Daniele >> >> -- >> 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. >> >> > -- > 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. > -- 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.
Re: Custom error pages, we *really* need them
+1 Maybe the generic page could be a fail Koi On Wed, Sep 15, 2010 at 7:31 AM, Daniele wrote: > Hi, > as you can see from the status page in the past 2 days Heroku had a > lot of problems that resulted in "Timeout connection" and "Backlog Too > Deep" error pages. This two pages have a message specifically > addressed to the administrator that is not acceptable in a production > site. We need to have personalized pages. Same logic about the Heroku > Ouchie Page of course! > > If this is not possible immediately a quick hack could be to have a > really generic "white-label" page (multilingual would be appreciated) > and put all the system message in an html comment. We are tech guys, > right? Is not a problem to look at the source to find out what is > happening. This seems clever that show a ugly error message to > everyone. > > Finally as I already suggested in another discussion: > A simple solution for more personalization without the need to access > any preferences could be to have a full page iframe inside the > heroku's error page pointing to http://error > ./.html > The admin has to create a third/fourth level domain, point it to a > different server and create the personalized pages. > So every application can have an error page/backup application to > handle the down. A js can check for the domain existence and switch to > a plain txt message if it is not set. > > I'd love to get feedback on these ideas by Heroku guys. Thank you. > > Daniele > > -- > 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. > > -- 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.
Custom error pages, we *really* need them
Hi, as you can see from the status page in the past 2 days Heroku had a lot of problems that resulted in "Timeout connection" and "Backlog Too Deep" error pages. This two pages have a message specifically addressed to the administrator that is not acceptable in a production site. We need to have personalized pages. Same logic about the Heroku Ouchie Page of course! If this is not possible immediately a quick hack could be to have a really generic "white-label" page (multilingual would be appreciated) and put all the system message in an html comment. We are tech guys, right? Is not a problem to look at the source to find out what is happening. This seems clever that show a ugly error message to everyone. Finally as I already suggested in another discussion: A simple solution for more personalization without the need to access any preferences could be to have a full page iframe inside the heroku's error page pointing to http://error./.html The admin has to create a third/fourth level domain, point it to a different server and create the personalized pages. So every application can have an error page/backup application to handle the down. A js can check for the domain existence and switch to a plain txt message if it is not set. I'd love to get feedback on these ideas by Heroku guys. Thank you. Daniele -- 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.
Re: Custom Error Pages
What if there was a special branch in your app's repo called "error-pages" or something, similar to Github's gh-pages branch. That branch would ONLY have things like 500.html, 404.html, etc. Those static pages could then pushed somewhere other than the dynos, and served in case of dyno issues. On Fri, Aug 6, 2010 at 9:30 AM, James Bracy wrote: > +1, especially for the backlog to deep. > > On Fri, Aug 6, 2010 at 4:54 AM, Idris wrote: > > +1 for this feature. If we could just upload static HTML pages for > > the different possible heroku errors, that would be great. It's > > unacceptable for a Heroku branded error to come up no matter what the > > error is. > > > > On Aug 6, 6:41 am, Tomaž Žlender wrote: > >> +1 for this feature. > >> > >> On Jul 27, 6:20 am, daniel hoey 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 > . > > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > > > > > -- > 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. > > -- 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.
Re: Custom Error Pages
+1, especially for the backlog to deep. On Fri, Aug 6, 2010 at 4:54 AM, Idris wrote: > +1 for this feature. If we could just upload static HTML pages for > the different possible heroku errors, that would be great. It's > unacceptable for a Heroku branded error to come up no matter what the > error is. > > On Aug 6, 6:41 am, Tomaž Žlender wrote: >> +1 for this feature. >> >> On Jul 27, 6:20 am, daniel hoey 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. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- 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.
Re: Custom Error Pages
+1 for this feature. If we could just upload static HTML pages for the different possible heroku errors, that would be great. It's unacceptable for a Heroku branded error to come up no matter what the error is. On Aug 6, 6:41 am, Tomaž Žlender wrote: > +1 for this feature. > > On Jul 27, 6:20 am, daniel hoey 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Custom Error Pages
I'd also like to see ways of customising the backlog too deep, and timeout pages too - it's not great for a user to see pages from a seemingly random place when things aren't behaving as they should. N 2010/8/6 Tomaž Žlender > +1 for this feature. > > On Jul 27, 6:20 am, daniel hoey 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 > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- Neil Middleton -- 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.
Re: Custom Error Pages
+1 for this feature. On Jul 27, 6:20 am, daniel hoey 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Custom Error Pages
+1 for the unbranded page A simple solution for more personalization without the need to access any preferences could be to have a full page iframe inside the heroku's error page pointing to http://error.. So every application can have an error page/backup application to handle the down. A js can check for the domain existence and switch to a plain txt message if it is not set. On 5 Ago, 22:46, James Miller wrote: > 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. -- 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.
Re: Custom Error Pages
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 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 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 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 > > . > > 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.
Re: Custom Error Pages
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 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 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 > . > 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.
Re: Custom Error Pages
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 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Re: Custom Error Pages
We definitely require something like this, Right now it is very hard dealing with errors. We understand that you guys are trying to keep as up to date as possible and deeply appreciate that. But it is a production platform and a custom error message is the least we can offer our clients when something in heroku is failing. On Jul 26, 11:20 pm, daniel hoey wrote: > Is there anyway to use our ownerrorpages 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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
Custom Error Pages
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. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
