>-----Original Message----- >From: Pid [mailto:p...@pidster.com] >Sent: Friday, November 30, 2012 3:13 PM >To: Tomcat Users List >Subject: Re: Error page messages > >On 30/11/2012 22:09, Leo Donahue - RDSA IT wrote: >>> -----Original Message----- >>> From: Pid [mailto:p...@pidster.com] >>> Sent: Friday, November 30, 2012 3:04 PM >>> To: Tomcat Users List >>> Subject: Re: Error page messages >>> >>> On 30/11/2012 21:00, Leo Donahue - RDSA IT wrote: >>>> Are there standardized server responses that one should expect to >>>> see >>> when dealing with java.lang, javax.servlet and javax.faces exceptions >>> that should be displayed to the client? >>> >>> You mean status codes or error pages? >> >> Error pages. >> >>> >>> If an exception isn't handled* by the app then it's 500 and a >>> stacktrace if you haven't configured a custom error page. Those >>> packages probably have a few tens of exceptions that could be thrown. >>> >>> >>>> I don't know that I would expect to see any of these on a public >>>> website, as I >>> am likely not to care what happens on the server I'm browsing, as >>> long as the server can recover/redirect. >>> >>> Catch them at the appropriate point in your code, or configure a custom >error page. >> >> And what kind of information does one show the user in a custom error >page? I don't know of any public facing websites, off hand, that show >uncaught exception messages. I was just trying to decide what I would show, >if anything, if I configured a custom error page for certain types of >exceptions, >such as java.lang, or javax.servlet, or javax.faces. > >A polite message saying "oops", or a fail whale, or a unicorn... > > >p
Good options, and very tempting. Maybe one of these? http://tinyurl.com/bvl2gko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
